-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvements to rpm-ch #51
base: master
Are you sure you want to change the base?
Conversation
Hi,
Overall I tried to not add even more options to commands but rather have separate commands (likg gbp tag) since this makes it less confusing for users. |
What do you think it should commit? Just the changelog? I found it useful to be able to include other changes to the commit (by doing git-add before invoking gbp-rpm-ch)
Yes, I basically agree on that. However, the idea behind the committing/tagging options here is that you can automatically include the correct tag name in the changelog entry that you're committing/tagging. The rpm changlog entry has a version revision field and one option is to use the packaging tag there. |
b014201
to
d07ad16
Compare
Make it possible for git commands to output directly to stdout without redirection (i.e. capturing their stdout stream). Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Previously the editor would not show in the shell because stdout was captured. Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
For setting the committer name/email/date - similarly to author_info. Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
For setting the committer name/email/date - similarly to author_info. Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Commit the changes to Git. Using this option will commit the changelog modifications as well as all other staged changes, making it possible to easily include other changes in the commit, too. Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Defines format string used to generate the commit message when --commit option is used. Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Implement '--tag' command line option (and other related options for e.g. signing) for creating and tagging a release. These correspond the tagging options in gbp-buildpackage-rpm. A slight difference is that gbp buildpackage-rpm never commits anything to git. However, in rpm-ch the '--tag' option automatically enables --commit which causes the changelog modifications (and, all other staged changes) to be committed to git before creating the tag. This makes it possible to create a release and document the packaging/release tag name in the rpm changelog. Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
This option can be used to directly give the text for new changelog entry, skipping auto-generation from git commit history entirely. Thus, '--since' or '--all' do not have any effect when '--message' is defined. Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
If defined, rpm-ch uses all commits from the Git history. This can be useful when creating a new changelog from scratch. Using '--all' causes '--since' to be ignored. Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
This gives the user the possibility to define what meta tags (in git commit message) gbp-rpm-ch recognizes as bug tracking system references. Alternatively, it makes it possible to disable bts meta tag parsing altogether. Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
d07ad16
to
b14ee9b
Compare
Makes it easier to run full unit tests on rpm based systems