Open cociweb opened 1 month ago
The pull request introduces several modifications to GitHub Actions workflow files. The builder.yaml
workflow now only allows manual execution, while lint.yaml
and tester.yaml
have adjustments to their triggering conditions. Additionally, a new workflow, release-notes.yaml
, has been added to automate changelog creation and release management. The CHANGELOG.md
has also been updated to improve formatting and maintain a history of version changes.
File | Change Summary |
---|---|
.github/workflows/builder.yaml |
Removed push event trigger for main branch and version tags; kept workflow_dispatch for manual runs. |
.github/workflows/lint.yaml |
Adjusted pull_request trigger to remove branch specification; push now only specifies main . |
.github/workflows/release-notes.yaml |
Introduced new workflow to automate changelog creation and release management on tag pushes. |
.github/workflows/tester.yaml |
Changed triggering condition to restrict workflow to only the main branch. |
ebusd/CHANGELOG.md |
Updated changelog format and retained entries for versions 23.2.6 to 23.2.0 with respective updates. |
lint.yaml
workflow configuration regarding triggers are relevant as they involve modifications to GitHub Actions workflows, similar to the changes made in the builder.yaml
workflow in the main PR.In the meadow where we play,
Workflows dance and change today.
With triggers set and notes to write,
Changelogs shine, oh what a sight!
Hops of joy, we celebrate,
In code we trust, we innovate! 🐇✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
@tjorim, could you please apply this patch to your updated fork and then create a new github release (with tag pattern of v0.0.0/V0.0.0/0.0.0) ? To ensure the PR does not introduce further issues according to the patch, consider making a release prior to applying the patch as well. Unfortunately, Lukas unable to test it, as it impacts the main branch. I've tested it previously on my main branch, but a confirmation would be beneficial.
As part of the pass criteria, the CHANGELOG.md must be updated to include the body text of the new release in markdown format, and the config.yaml must reflect the tag name in its version record.
@tjorim @LukasGrebe
the ebusd 24.1 is in the tube. Can we merge this before we release that?
I should have some time tonight or tomorrow to test out this PR so we are ready to ship once the alpine package bump is merged.
@tjorim Do You have any feedback?
This PR enables appending the changelog.md with the content (body) of a new GitHub Release. Consequently, building and publishing can be initiated by creating a new release (tagged with v0.0.0/V0.0.0/0.0.0 format) or manually through the dispatcher. Publishing will no longer be triggered by merges or pushes.
ATTENTION! Unfortunatelly, I'm not able to make a final test on my main branch, because the coderabbit 'hops' all the commit into this PR.
Summary by CodeRabbit