Repository navigation
[Chore] Forbid citing umbrella tickets as references - #24
Open
Martoon-00 wants to merge 1 commit into
Open
Martoon-00 wants to merge 1 commit into
Martoon-00 wants to merge 1 commit into
Conversation
Martoon-00
force-pushed
the
martoon/adjustments
branch
from
October 20, 2026 12:22
e992b6e to
96db769
Compare
Martoon-00
force-pushed
the
martoon/no-umbrella-ticket-refs
branch
2 times, most recently
from
October 20, 2026 12:23
2b85b94 to
f599385
Compare
Martoon-00
force-pushed
the
martoon/no-umbrella-ticket-refs
branch
from
October 20, 2026 12:29
f599385 to
2d6296e
Compare
Problem: agents cite a project's YouTrack umbrella ticket (used only for time tracking) as the issue reference in changelog entries, even though it is unrelated to the change. Solution: instruct that changelog entries, commits and PRs must refer only to the issue the change addresses, never to a project-wide ticket. Mark the umbrella ticket in `PROJECT.md` as time-tracking only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Martoon-00
force-pushed
the
martoon/no-umbrella-ticket-refs
branch
from
October 20, 2026 12:33
8e97090 to
cb986d5
Compare
heitor-lassarote
approved these changes
Oct 20, 2026
heitor-lassarote
left a comment
heitor-lassarote
left a comment
Member
There was a problem hiding this comment.
Did you check with gromak whether using [Chore] or None (for resolved issue) is fine? I tried looking for it in Slack, and I can't find it anymore, but he told me that we should prefer creating GitHub issues instead. To be fair, I think his guidance to me was about creating GH issues instead of YouTrack tickets for public repos. I'm in favor of using [Chore] for tiny tasks too and historically this is what we've been doing at Serokell, so perhaps my concern is moot, but it's good to ask.
The rest of the changes look good to me.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Problem: agents cite a project's YouTrack umbrella ticket (used only for time tracking) as the issue reference in changelog entries, even though it is unrelated to the change.
Solution: instruct that changelog entries, commits and PRs must refer only to the issue the change addresses, never to a project-wide ticket. Mark the umbrella ticket in
PROJECT.mdas time-tracking only.Related issue(s)
None — small maintenance of the skills.
✅ Checklist for your Pull Request
Related changes (conditional)
Tests
silently reappearing again.
Documentation
Agent instructions (conditional)
it followed the agent instructions in
plugins/serokell-global/skills/and
.github/copilot-instructions.md.Public contracts
of Public Contracts policy.
and
Stylistic guide (mandatory)
🤖 Generated with Claude Code