feature: support .issuetracker file
#1567
Closed
Conversation
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
sina-hide
force-pushed
the
support-.issuetracker-file
branch
2 times, most recently
from
33325df to
ed327fd
Compare
Beforehand issue trackers could be defined in the repository configuration only. They were stored in the `.git` directory. As a consequence each SourceGit user had to configure issue trackers for himself. Now additional issue tracker rules are read from an existing `.issuetracker` file (sourcegit-scm#1424). An issue tracker configured by a user has a higher priority than an issue tracker read from `.issuetracker`. This allows to share issue trackers between team members. SourceGit does not (yet?) write into the `.issuetracker` file. But using `git config` allows the user to easily construct issue tracker rules for the `.issuetracker` file, where even the escaping of the backslash in '#(\d+)' is done correctly. A `.issuetracker` file was added to SourceGit. It was created by executing the following commands in a bash shell, where the current directory was the repository root: ```bash cat >.issuetracker <<EOF # Integration with Issue Tracker # # (note that '\' need to be escaped). EOF git config set --file .issuetracker issuetracker.GitHub.regex '#(\d+)' git config set --file .issuetracker issuetracker.GitHub.url \ 'https://github.com/sourcegit-scm/sourcegit/issues/$1' ```
sina-hide
force-pushed
the
support-.issuetracker-file
branch
from
ed327fd to
6de9147
Compare
|
I've rebased onto the current |
love-linger
added a commit
that referenced
this pull request
Jul 18, 2025
…1567) Signed-off-by: leo <[email protected]>
|
I've pushed my implementation of this feature. Now you can share issuetracker rules by enable 
|
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.
Beforehand issue trackers could be defined in the repository configuration only. They were stored in the
.gitdirectory. As a consequence each SourceGit user had to configure issue trackers for himself.Now additional issue tracker rules are read from an existing
.issuetrackerfile (#1424). An issue tracker configured by a user has a higher priority than an issue tracker read from.issuetracker.This allows to share issue trackers between team members.
SourceGit does not (yet?) write into the
.issuetrackerfile. But usinggit configallows the user to easily construct issue tracker rules for the.issuetrackerfile, where even the escaping of the backslash in '#(\d+)' is done correctly.A
.issuetrackerfile was added to SourceGit. It was created by executing the following commands in a bash shell, where the current directory was the repository root: