You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add Contribution section into README, including the guidelines for
adding changelog metadata to the commit messages. Thanks to this,
changelog can be automatically generated while staying useful.
Here's the most direct way to get your work merged into the project.
120
+
121
+
1. Fork the project
122
+
1. Clone down your fork
123
+
1. Implement your feature or bug fix and commit changes
124
+
1. If the change fixes a bug at [Red Hat bugzilla](https://bugzilla.redhat.com/), or if it is important to the end user, add the following block to the commit message:
125
+
126
+
= changelog =
127
+
msg: message to be included in the changelog
128
+
type: one of: bugfix/enhancement/security (this field is required when message is present)
129
+
resolves: URLs to bugs or issues resolved by this commit (can be specified multiple times)
130
+
related: URLs to any related bugs or issues (can be specified multiple times)
131
+
132
+
* For example::
133
+
134
+
= changelog =
135
+
msg: Decode package URL when using for local filename
* For your convenience, you can also use git commit template by running the following command in the top-level directory of this project:
140
+
141
+
git config commit.template ./.git-commit-template
142
+
143
+
1. In a separate commit, add your name into the [authors file](https://github.com/rpm-software-management/librepo/blob/master/AUTHORS) as a reward for your generosity
144
+
1. Push the branch to your fork
145
+
1. Send a pull request for your branch
146
+
117
147
## Links
118
148
119
149
*[Red Hat Bugzilla](https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=VERIFIED&component=librepo)
0 commit comments