| Age | Commit message (Collapse) | Author |
|---|
|
* Bump actions/labeler from 4 to 5
Bumps [actions/labeler](https://github.com/actions/labeler) from 4 to 5.
- [Release notes](https://github.com/actions/labeler/releases)
- [Commits](https://github.com/actions/labeler/compare/v4...v5)
---
updated-dependencies:
- dependency-name: actions/labeler
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
* Update config file format to account for incompatible changes.
* Properly fix the labeler config.
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Austin S. Hemmelgarn <austin@netdata.cloud>
|
|
Instead of flagging on the git ref for the run, flag on the repository
ID and PR number. This ensures that previous runs get cancelled only
for the correct PR when a new run is triggered.
This should fix the seemingly random cases of PR labeler runs being
cancelled for no apparent reason on our PRs.
|
|
This has a number of advantages:
- It allows us to make PR labeling event-driven instead of polling.
This, in turn, means that it only runs when a PR is modified, and only
evaluates that specific PR, which results in spending far less time
running PR labeler jobs.
- This is the ‘official’ way to handle PR labels automatically as code,
and thus Ilya will no longer need to maintain a custom labeling action
for this purpose.
- The matching syntax supported by this action is more expressive than
what is supported by our existing infrastructure, allowing for things
sucha s requring all of a group of files to be modified in a PR for it
to have a specific label applied. We have no need right now for this,
but it is useful to have it available long-term.
- Because the labeling is PR-triggered, it shows up in the PR checks, so
we can more easily see if auto-labeling has run for a given PR or not.
|
|
|
|
|
|
|
|
It skews our data in (probably) strange ways.
|
|
* github/labeler: add Dockerfile* pattern to area/packaging label
* github/labeler: switch to v0.1.0
|
|
* .github/workflow: switch from paulfantom/periodic-labeler to ilyam8/periodic-pr-labeler
* .github/labeler: backends pattern fix
|
|
|
|
This updates the PR labeling via GHA to not depend on the access level
of the owner of the PR relative to the repository, which should finally
make it work correctly.
|
|
This updates the access token in the labeler action to use permissions
of the netdatabot account instead of using the generic access token
provided by GitHub.
This allows the labeling to work correctly even for forks owned by
people who do not have write access to the repo.
|
|
This decouples the PR labeling process from the main CI process, allowing
them to run completely independenly of each other.
The new labeling configuration is based on copying, extending, and
correcting the existing labeling rules in the `labeler.sh` script which
the commit is removing.
Labeling is configured through `.github/labeler.yml` file. Check there
for info on the exact format.
The exact configuration being used will update labels on PR's whenever
one is opened, updated, reopened, or marked ready for review. It will
not remove existing labels from the PR, only add new ones.
|
