Skip to content
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

Triggers, messaging, release notes in changelog CI #45

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

JesperDramsch
Copy link
Member

  1. Changes when the CI is run.

This avoids "bad runs" if a release fails, as it depends on a successful workflow run.

  1. Copies the generated release note to the changelog

This intends to reduce merge conflicts due to individually updated changelogs.

  1. Big red message in PR to merge

This adds a note to the PR message to not squash to help users perform the correct action.

1. Changes when the CI is run.

This avoids "bad runs" if a release fails, as it depends on a successful workflow run.

2. Copies the generated release note to the changelog

This intends to reduce merge conflicts due to individually updated changelogs.

3. Big red message in PR to merge

This adds a note to the PR message to not squash to help users perform the correct action.
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.76%. Comparing base (93bd60e) to head (58fc03c).
Report is 2 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #45   +/-   ##
========================================
  Coverage    88.76%   88.76%           
========================================
  Files            3        3           
  Lines           89       89           
========================================
  Hits            79       79           
  Misses          10       10           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants