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
Copy file name to clipboardExpand all lines: docs/use.md
+54Lines changed: 54 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,6 +64,60 @@ You can choose to *remove* some types of PRs from your changelog by passing the
64
64
left-most column above.
65
65
```
66
66
67
+
### Pull Requests with Multiple Matching Labels
68
+
69
+
If a pull request has multiple labels that match different categories, it will appear in **only the first matching section** based on the order of categories processed. For example, a PR labeled with both `api-change` and `enhancement` will appear only in the "API and Breaking Changes" section, not in "Enhancements made".
70
+
71
+
The categories are processed in this order: `api_change`, `new`, `deprecate`, `enhancement`, `bug`, `maintenance`, `documentation`, `ci`. This ensures each PR appears exactly once in the changelog, preventing duplication across sections.
72
+
73
+
## Include Pull Request reviewers and commenters in your changelog
74
+
75
+
By default, GitHub Activity will include any _reviewer_ of a pull request in the item for that PR. This looks like the following:
76
+
77
+
## Include a list of all contributors at the end of your changelog
78
+
79
+
By default, this tool will include a long list of contributors at the end of your changelog. This is the unique set of all contributors that contributed to the release.
GitHub Activity tries to automatically determine the unique list of contributors within a given window of time.
86
+
There are many ways to define this, and there isn't necessarily a "correct" method out there.
87
+
88
+
We try to balance the two extremes of "anybody who shows up is recognized as contributing" and "nobody is recognized as contributing".
89
+
We've chosen a few rules that try to reflect sustained engagement in issues/PRs, or contributions in the form of help in _others'_ issues or contributing code.
90
+
91
+
Here are the rules we follow for finding a list of contributors within a time window. A contributor is anyone who has:
92
+
93
+
- Contributed to a PR merged in that window (includes opening, merging, committing, commenting, or committing)
94
+
- Commented on >= 2 issues that weren't theirs
95
+
- Commented >= 6 times on any one issue
96
+
- Known bot accounts are generally not considered contributors
97
+
98
+
We'd love feedback on whether this is a good set of rules to use.
99
+
100
+
## Strip PR type metadata from the changelog titles
101
+
102
+
If you follow the [title prefix convention used to split PRs](#prefixes-and-tags), you can remove these prefixes when you generate your changelog, so that they don't clutter the output.
103
+
104
+
To strip title prefix metadata, use the `--strip-brackets` flag.
105
+
106
+
For example, `[DOC] Add some documentation` will be rendered as `Add some documentation`.
107
+
108
+
## Change the heading level for your changelog items
109
+
110
+
To change the starting heading level for changelog items, use the `--heading-level N` flag. Where `N` is the starting heading level (e.g., `2` corresponds to `##`).
111
+
112
+
This is useful if you want to _embed_ your changelog into a larger one (e.g., `CHANGELOG.md`).
113
+
114
+
## Include issues in your changelog
115
+
116
+
To include closed issues in your changelog, use the `--include-issues` flag.
117
+
118
+
## Include opened issues in your changelog
119
+
120
+
To include issues and Pull Requests that were _opened_ in a time period, use teh `--include-opened` flag.
- checking for toc modification time [#772](https://github.com/jupyter-book/jupyter-book/pull/772) ([@choldgraf](https://github.com/choldgraf), [@chrisjsewell](https://github.com/chrisjsewell))
13
16
- first pass toc directive [#757](https://github.com/jupyter-book/jupyter-book/pull/757) ([@choldgraf](https://github.com/choldgraf), [@AakashGfude](https://github.com/AakashGfude))
0 commit comments