-
Notifications
You must be signed in to change notification settings - Fork 140
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
♻️ [RUM-159] Categorize changes as public or internal in the CHANGELOG #2851
♻️ [RUM-159] Categorize changes as public or internal in the CHANGELOG #2851
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2851 +/- ##
==========================================
- Coverage 93.66% 93.64% -0.02%
==========================================
Files 266 266
Lines 7573 7573
Branches 1683 1683
==========================================
- Hits 7093 7092 -1
- Misses 480 481 +1 ☔ View full report in Codecov by Sentry. |
Bundles Sizes Evolution
🚀 CPU Performance
🧠 Memory Performance
|
const START_WITH_EMOJI = /^\p{Emoji_Presentation}/u | ||
|
||
const PUBLIC_EMOJI_PRIORITY = ['💥', '✨', '🐛', '⚡️', '📝', '⚗️'] | ||
const INTERNAL_EMOJI_PRIORITY = ['👷', '🎨', '🧪', '✅', '👌', '♻️', '🔧', '📄', '🔇', '🔊', '📦'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥜 nitpick: I would reorder the table to put the emojis of the same "nature" close to one another:
['👷', '🔧', '📦', // build conf
'♻️', '🎨', // refactoring
'🧪', '✅', // tests
'🔇', '🔊', // telemetry
'👌', '📄']
/to-staging |
🚂 Branch Integration: starting soon, median merge time is 11m Commit 51a8e2be4b will soon be integrated into staging-28. Use |
) into staging-28 Integrated commit sha: 51a8e2b Co-authored-by: roman.gaignault <[email protected]>
🚂 Branch Integration: This commit was successfully integrated Commit 51a8e2be4b has been merged into staging-28 in merge commit 21eb08f0d0. Check out the triggered pipeline on Gitlab 🦊 |
${internalChanges.join('\n')} | ||
`.replace(/\(#(\d+)\)/gm, (_, id) => `([#${id}](https://github.com/DataDog/browser-sdk/pull/${id}))`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❓ question: this is nice, but why is it done only for internal changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks ! What do you mean only for internal changes ? it's replacing for internal and public I guess
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah sorry I misread! Looks fine then.
|
||
const CHANGELOG_FILE = '../../CHANGELOG.md' | ||
const CONTRIBUTING_FILE = '../../CONTRIBUTING.md' | ||
const PUBLIC_EMOJI_PRIORITY = ['💥', '✨', '🐛', '⚡️', '📝', '⚗️'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'\u26a1\ufe0f'
but should be only '\u26a1'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch 👍 I will update this in the next Pr
|
||
const CHANGELOG_FILE = '../../CHANGELOG.md' | ||
const CONTRIBUTING_FILE = '../../CONTRIBUTING.md' | ||
const PUBLIC_EMOJI_PRIORITY = ['💥', '✨', '🐛', '⚡️', '📝', '⚗️'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💭 thought: '⚗️' should be internal I think
Motivation
When we created the CHANGELOG, we chose to only show public changes (bug fixes, new features, …).
In practice, this is not always respected. Sometimes, it’s not clear whether it is a public or internal change. We are a bit hesitant to show experimental features or not. Sometimes we do releases with only internal changes, and having an empty entry is not ideal.
Changes
Let’s add everything, but to help the reading, split changes into two sections (ex: public/internal changes). The generate_changelog script should handle the formating based on gitmojis.
Testing
I have gone over the contributing documentation.