| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
This is because we reference to deprecated.txt from news.txt, so
deprecation news updates are made only in deprecated.txt.
|
| |
|
|
|
| |
There is a "performance" section in news.txt so it makes sense we should
also give a reminder to update news for performance improvements.
|
| |
|
|
|
|
|
|
|
|
| |
Setting the label `ci:skip-news` will skip the job. This is useful for
maintainers to indicate to contributors that a feature isn't big enough
to warrant a news entry, or for contributors who dislike red CI even if
there's nothing wrong.
Also change label `ci-s390x` to `ci:s390x`; this way it'll be easier to
see that `ci:` are a subcategory of labels that affect CI in some way.
|
| |
|
|
|
| |
Mostly rename file and variable names to be more consistent. This makes
it easier to locate them in the "Actions" tab on github.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [actions/checkout](https://github.com/actions/checkout) from 3 to 4.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v3...v4)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| | |
|
| |
|
|
| |
news.txt is only meant as a reminder, but contributors have no way of
knowing this automatically without such a message.
|
| |
|
|
|
| |
The default merge branch is unreliable when trying to determine number
of commits in a PR. Using the HEAD branch of the PR removes this
ambiguity.
|
| |
|
|
| |
We seem to need the parent commit of the earliest PR commit in order to
perform common git functionality to check which files were changed.
|
|
|
If any commit message in the PR is either of type "feat" or is a
breaking change, then there's a high probability that news.txt should be
updated. Give an error if news.txt hasn't been updated in that case.
This workflow cannot 100% correctly determine if news.txt should be
updated even if the commit messages were exactly correct. The entries in
news.txt is determined by changes between releases, while the commit
messages are based on the master branch. While it is an approximation,
it is still a useful enough one that it's still valuable to have this
job as a reminder even if it gives an error if it shouldn't. In these
cases it is perfectly fine to ignore the failure for this job.
|
