Git issue tracker
This app track changes in git by receiving web hook from BitBucket and synchronize found issues with Jira in terms of fix version. So it gives 100% guarantee that fix version is set correctly.
BitBucket or Jira could be changed to any other Git or Bug tracker system (should be written by your own).
How does it work
- Webhook (on push) should be set up on the git server.
- Git itself should be installed where this application is started
- Extend
IssueHandlerand implement your own workflow with your bug-tracker system. IE, set fixVersion directly to each task or only for story without subtasks or just add comment where it was merged. For myself I used it together with automationforjira for further no-code processing of received data. - Extend
WebHookDataParserif you use as git server something different from BitBucket.
Variables to override if needed
TRACKED_BRANCH_REGEXP: which branches do we track, by default it is set to(release/.*|hotfix/.*|support/.*|develop|dev). Here is used git-flow branch modelMERGE_PATTERN_SEARCH_TO_SKIP: merge pattern which should not be tracked, by default it is set toMerge.*((release\/|support\/|hotfix\/)|(tag)).*(develop|dev).*.WHITE_LISTED_REPOS: repositories' name which available for further processing, by default
1 maintainer
Metadata
1 maintainer
Release files for git-issue-tracker 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| git-issue-tracker-0.1.1.tar.gz | 6.7 kB | Without provenance | Details for git-issue-tracker-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| git_issue_tracker-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for git_issue_tracker-0.1.1-py3-none-any.whl |
Total release size: 16.6 kB
Release files / git-issue-tracker-0.1.1.tar.gz
| Download URL | git-issue-tracker-0.1.1.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af323e60114ca7db1d52bbaf75d02a70dc54c626bdfd53ce29fd924ad1c12d3b
|
|
BLAKE2b-256 checksum How to use checksums |
9238b3920935b43a17c2994c9efb2c5f5debe5bcd42bd589d8d53c16421524e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.10
|
Release files / git_issue_tracker-0.1.1-py3-none-any.whl
| Download URL | git_issue_tracker-0.1.1-py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
047e71e4d288398bc7097aeb1af0a2526a8628db0fd660cd44c6a874290367e5
|
|
BLAKE2b-256 checksum How to use checksums |
47ad31d6e8df47e590bee0965ec41b8c418d72a374585452f604f2c8f4cb022d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.10
|
Security for git-issue-tracker 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
