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
Automate changelog #4743
Automate changelog #4743
Conversation
New changie release for the pre-release request. Need to look into how it works but will hopefully replace the manual script I wrote! Edit: This release 100% replaced my last custom script! |
👋 Thanks for adding a changelog entry! |
👋 Thanks for adding a changelog entry! Delete this before the end. It's really just here to test output. |
1 similar comment
👋 Thanks for adding a changelog entry! Delete this before the end. It's really just here to test output. |
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.
This looks great! I'm on the fence about this, but should we include changie as part of the Makefile
? I opted to add it for pre-commit, but this feels somewhere inbetween a developer's choice thing and a required thing.
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 am sooooo looking forward to this!
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 didn't take a close enough look at the action and the templates yet but I wanted to leave the note about make dev
.
.changes/README.md
Outdated
### Workflow | ||
|
||
#### Daily workflow | ||
Each code change gets a changlog file by running `changie new` and following the prompts. This ensures correct file format and file name. |
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.
to run changie new
should we add it to be installed with make dev
?
|
||
We use [changie](https://changie.dev) to generate `CHANGELOG` entries. Do not edit the `CHANGELOG.md` directly. Your modifications will be lost. | ||
|
||
Follow the steps to [install `changie`](https://changie.dev/guide/installation/) for your system. |
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.
if we use make dev
this instruction could change to reflect that.
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.
To close the loop from a slack conversation, we can't add changie to make dev
as it isn't available through pip. If this becomes an issue we'll explore some alternative ways to make changie available.
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.
This is great!!! One question, what will happen to the original changelog?
@ChenyuLInx The original changelog is saved as a markdown file in Every time |
footerFormat: | | ||
Contributors: | ||
{{- $contributorDict := dict }} | ||
{{- $core_team := list "emmyoop" "nathaniel-may" "gshank" "leahwicz" "ChenyuLInx" "stu-k" "iknox-fa" "VersusFacit" "McKnight-42" "jtcohen6" }} |
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.
This can be a good first issue for new hires to just add themselves to this list
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 there a single running list of things like this somewhere?
I don't like that this is hardcoded but I'm not seeing a way around it at the moment.
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'm not sure if we can use GitHub's team concept to get this list. We have the Core team which contains all the handles. For this PR, I'm ok with the hardcoded list but then thinking about improvements after that
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.
The Github API looks like it has a way to do it via the returned "login" field, but it would involve mapping over the returned list. I agree it would be good for a subsequent improvement.
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.
LGTM!
This reverts commit 490bda8.
5660596
to
1f39de2
Compare
* initial setup to use changie * added `dbt-core` to version line * fix formatting * rename to be more accurate * remove extra file * add stug for contributing section * updated docs for contributing and changelog * first pass at changelog check * Fix workflow name * comment on handling failure * add automatic contributors section via footer * removed unused initialization * add script to automate entire changelog creation and handle prereleases * stub out README * add changelog entry! * no longer need to add contributors ourselves * fixed formatted and excluded core team * fix typo and collapse if statement * updated to reflect automatic pre-release handling Removed custom script in favor of built in pre-release functionality in new version of changie. * update contributing doc * pass at GHA * fix path * all changed files * more GHA work * continued GHA work * try another approach * testing * adding comment via GHA * added uses for GHA * more debugging * fixed formatting * another comment attempt * remove read permission * add label check * fix quotes * checking label logic * test forcing failure * remove extra script tag * removed logic for having changelog * Revert "removed logic for having changelog" This reverts commit 490bda8. * remove unused workflow section * update header and readme * update with current version of changelog * add step failure for missing changelog file * fix typos and formatting * small tweaks per feedback * Update so changelog end up onlywith current version, not past * update changelog to recent contents * added the rest of our releases to previous release list * clarifying the readme * updated to reflect current changelog state * updated so only 1.1 changes are on main # Conflicts: # CHANGELOG.md
* Automate changelog (#4743) * initial setup to use changie * added `dbt-core` to version line * fix formatting * rename to be more accurate * remove extra file * add stug for contributing section * updated docs for contributing and changelog * first pass at changelog check * Fix workflow name * comment on handling failure * add automatic contributors section via footer * removed unused initialization * add script to automate entire changelog creation and handle prereleases * stub out README * add changelog entry! * no longer need to add contributors ourselves * fixed formatted and excluded core team * fix typo and collapse if statement * updated to reflect automatic pre-release handling Removed custom script in favor of built in pre-release functionality in new version of changie. * update contributing doc * pass at GHA * fix path * all changed files * more GHA work * continued GHA work * try another approach * testing * adding comment via GHA * added uses for GHA * more debugging * fixed formatting * another comment attempt * remove read permission * add label check * fix quotes * checking label logic * test forcing failure * remove extra script tag * removed logic for having changelog * Revert "removed logic for having changelog" This reverts commit 490bda8. * remove unused workflow section * update header and readme * update with current version of changelog * add step failure for missing changelog file * fix typos and formatting * small tweaks per feedback * Update so changelog end up onlywith current version, not past * update changelog to recent contents * added the rest of our releases to previous release list * clarifying the readme * updated to reflect current changelog state * updated so only 1.1 changes are on main # Conflicts: # CHANGELOG.md * updated to reflect current state of 1.0.latest * convert backports to changie entries
resolves #4652
Description
This adds changie to
dbt-core
!.changes
where the actual changelog files (yaml
ormd
) will live. This directory also contains a header file that will apply as a header to the entireCHANGELOG.md
.changie.yaml
defines what data is in a changelog entry as well as the format it will output into markdown.CONTRIBUTING
.yaml
in the appropriate directory as the file names are generated dynamically. It also provides an override where theSkip Changelog
label on a PR would allow the check to pass without the file.Pending
/.changes
is up to date for the most recent version of the master changelog.Checklist
CHANGELOG.md
and added information about my change