Repository navigation
Let the Linear label be configured, by id or by name - #124
Merged
Merged
Conversation
`linear.labelName` sets the label Dependicus puts on its Linear issues and finds them by. It defaults to "Dependicus", as before. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
srubin
reviewed
Oct 19, 2026
srubin
left a comment
srubin
left a comment
There was a problem hiding this comment.
Does anything break if you change the label name for an existing Dependicus deployment, i.e., would it no longer be able to find existing issues?
Collaborator
Author
|
That's correct, I think it would fail to find existing tickets. |
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
irskep
changed the title
Collaborator
Author
|
Tweaked so you can provide a name or an ID, and do an in-place rename. |
srubin
approved these changes
Oct 19, 2026
srubin
left a comment
srubin
left a comment
There was a problem hiding this comment.
Seems like a reasonable thing for teams to be able to control!
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.
I'm not 100% sure you'll want to accept this. Curious what you think.
I experimented with calling our label "Dependency Bump" instead of "Dependicus" because most teams don't care about the name of the tool that creates the tickets. So using "Dependency Bump" helps them put the ticket in context more than "Dependicus."
On the other hand, the label is the thing the tool uses to figure out which tickets were created by it. Using a more general label might obfuscate that.
Adds
linear.label. Dependicus puts that label on every Linear issue it files and uses it to find them again. It defaults to the name "Dependicus", so nothing changes for a config that does not set it.The label can be given by id or by name:
By id, Dependicus uses the label as is. Nothing is looked up or created, so a read-only API key is enough for a dry run. A name lookup is workspace-wide and ignores case, so an id also avoids picking a team label with the same name.
By name, Dependicus finds the label in the workspace and creates it if it is missing. That part needs an API key with write access.
A workspace that already has a label for dependency work can use it instead of getting a second one.
🤖 Generated with Claude Code