-
Notifications
You must be signed in to change notification settings - Fork 14
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
chore(scripts): improve release script with git diff [skip-bc] #3686
Conversation
No code generatedIf you believe code should've been generated, please, report the issue. 📊 Benchmark resultsBenchmarks performed on the method using a mock server, the results might not reflect the real-world performance.
|
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.
nice clean!!
continue; | ||
} | ||
|
||
// sometimes the scope of the commits is not set correctly and concerns another language, we can fix it. | ||
if (LANGUAGES.includes(validCommit.scope as Language) && validCommit.scope !== lang) { | ||
validCommit.message = validCommit.message.replace(`(${validCommit.scope}):`, `(${lang}):`); |
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.
is this reflected in the changelog? I'd rather keep it matching the git history but still include it in the new version computing if possible
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.
I find it weird to see a feat(python): add linter
in the java changelog
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.
can we replace it with feat(clients)
maybe then?
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.
sure
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.
just make the scope wider idk D: it's weird to differ from the git history imo but you are right
…ated) algolia/api-clients-automation#3686 Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
…ated) algolia/api-clients-automation#3686 Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
…ated) algolia/api-clients-automation#3686 Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
…ated) algolia/api-clients-automation#3686 Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
…ated) algolia/api-clients-automation#3686 Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
…ated) algolia/api-clients-automation#3686 Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
…ated) algolia/api-clients-automation#3686 Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
…ated) algolia/api-clients-automation#3686 Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
…ated) algolia/api-clients-automation#3686 Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
…ated) algolia/api-clients-automation#3686 Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
…ated) algolia/api-clients-automation#3686 Co-authored-by: Pierre Millot <pierre.millot@algolia.com>
🧭 What and Why
For the longest time, we based changelogs and release on the commit title only, but its often misleading or wrong.
Instead, we can use
git diff
to know exactly which commits impact which client, and based the release and changelog based of that.Also take the time to refactor and simplify the release script and lint the tests.
The changelog will automatically use the correct language scope also, even if the commit was wrong.