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

Skip towncrier check on 'nonews' label #1105

Conversation

johannaengland
Copy link
Contributor

This also changes that the check runs when a label is added/removed and on the default actions: when a PR is opened/reopened or the PR's head branch is updated.

It's fitting - this PR will also be right away used as test

Copy link

sonarqubecloud bot commented Jan 2, 2025

@johannaengland johannaengland added the nonews No news fragment is necessary for this PR (e.g. refactoring, cleanups, workflow/development changes) label Jan 2, 2025
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.83%. Comparing base (8ba9439) to head (072242a).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1105   +/-   ##
=======================================
  Coverage   79.83%   79.83%           
=======================================
  Files         145      145           
  Lines        5267     5267           
=======================================
  Hits         4205     4205           
  Misses       1062     1062           

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

@johannaengland johannaengland merged commit 2f28a64 into Uninett:master Jan 6, 2025
14 of 15 checks passed
@johannaengland johannaengland deleted the workflows/skip-towncrier-nonews-label branch January 6, 2025 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
nonews No news fragment is necessary for this PR (e.g. refactoring, cleanups, workflow/development changes)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants