git-redmine
Redmine integration to git.
Configuration
Add the following snippet to your .config/git/config file.:
[redmine] url = https://redmine.mycompany.org/ key = apikey OR username = username password = password
Usage
project
Show the current default project.
project set
Set the current default project for this repository, useful for creating new issues.:
git redmine project set myproject-id
rebase
Checkout master, pull origin/master on master then rebase current feature branch on master, if it fails it reset the branch. Checkout the original branch after all this.
git redmine rebase
issue new
Given a default project, create a new issue, an editor is launched to define subject and description of the issue.:
git redmine issue new
issue take
Handle the given issue by creating or switching to a branch named wip/<issue-number>-<slugified-issue-subject> forking from master.:
git redmine issue take 123
It will propose applying patches attached to the issue.
issue show
Show information about the current issue.:
git redmine issue show
Show informations about issue 9999.:
git redmine issue show --issue 9999
issue submit
It first does a git redmine rebase then use git format-patch to create the patch serie from master and attach it to the current issue. An editor is launched to add a commment.:
git redmine issue submit
To submit only the last commit:
git redmine issue submit 1
To submit the last commit to issue 9999:
git redmine issue submit --issue 9999 1
issue apply
Apply patches attached to the current issue.:
git redmine issue apply
Apply patched atteched to issue 9999.:
git redmine issue apply --issue 9999
link
git redmine link 9999
Link current branch issue to issue 9999.
merge-and-push
Merge current feature branch in a target branch (default is master), push target branch to origin, delete feature branch locally and on origin; if before that those operations pass: pull-rebase the target branch, rebase feature branch on target.
git rebase merge-and-push
clean
Remove local and remote branch for issues closed more than 21 days ago. Use –no-local to only clean local branches.
git redmine clean [–local/–no-local]
1 maintainer
Metadata
1 maintainer
Release files for git-redmine 1.1.0
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-redmine-1.1.0.tar.gz | 8.2 kB | Without provenance | Details for git-redmine-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| git_redmine-1.1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for git_redmine-1.1.0-py2.py3-none-any.whl |
Total release size: 16.5 kB
Release files / git-redmine-1.1.0.tar.gz
| Download URL | git-redmine-1.1.0.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6c5c187c65ed3057c0862115c91fbce3922d8e3ecc0f003dc281e6bc00ac35a0
|
|
BLAKE2b-256 checksum How to use checksums |
0baee2e5b580bc687aef67c5c1b811a48798ff5cdfd2b6acc0f667c7efbe7f2c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.4.2 requests/2.25.1 setuptools/52.0.0 requests-toolbelt/0.9.1 tqdm/4.57.0 CPython/3.9.2
|
Release files / git_redmine-1.1.0-py2.py3-none-any.whl
| Download URL | git_redmine-1.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
8684e23d1e5898a9d8ca8d6cf17cb5748eef9afd34edc664405960e9e7a21af6
|
|
BLAKE2b-256 checksum How to use checksums |
5ca35245f5d1ba43d1db2b39cfe80752f0daa2c169cca699d5f3fe67512986a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.4.2 requests/2.25.1 setuptools/52.0.0 requests-toolbelt/0.9.1 tqdm/4.57.0 CPython/3.9.2
|
Security for git-redmine 1.1.0
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.
