Files
ansible-docs/tests/pr_labeler.txt
Maxwell G 91ebd253b4 [stable-2.14] Backport pr_labeler changes (#1918)
* pr_labeler: improve create_boilerplate_comment logging

(cherry picked from commit 5730ba9a01)

* pr_labeler: add --force-process-closed flag

(cherry picked from commit 44ffe0f210)

* pr_labeler: add warning for porting_guides changes

This adds a warning message when PRs are created that edit
porting_guides by someone outside of the Release Management WG. These
files are automatically generated during the ansible release process and
should not be modified.

Fixes: https://github.com/ansible/ansible-documentation/issues/503
(cherry picked from commit d2e6625e8b)

* pr_labeler: use @release-management-wg team for porting_guide check

Instead of hardcoding the list of release managers, we can use the
Github API to retrieve the members of the
`@ansible/release-management-wg` team.

(cherry picked from commit dddfd7eb55)

* pr_labeler: exempt bots from porting_guide check

For example, patchback is not a release manager, but we still want it to
backport Porting Guide PRs.

(cherry picked from commit 746662c255)

* pr_labeler: improve porting_guide_changes template wording

Co-authored-by: Sandra McCann <samccann@redhat.com>
(cherry picked from commit 95ece7e9d6)

* pr_labeler: refactor new_contributor_welcome code (#990)

* pr_labeler: add GlobalArgs.full_repo property

* pr_labeler: refactor new_contributor_welcome code

As of https://github.com/ansible/ansible-documentation/issues/69, the
pr_labeler responds with a welcome message when an issue or PR is opened
by a new contributor. It turns out this never actually worked properly.

The previous method that relied on Github's `author_association` flag
did not work with the app token that the pr_labeler uses. This refactors
the code to figure out whether a user is a new contributor by
searching the list of issues and PRs.

Fixes: https://github.com/ansible/ansible-documentation/issues/204

* pr_labeler: address potential race condition

(cherry picked from commit 763815d1ad)

* Bump actions/setup-python from 4 to 5 (#966)

Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4 to 5.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](https://github.com/actions/setup-python/compare/v4...v5)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-type: direct:production
  update-type: version-update:semver-major
...

(cherry picked from commit 466b1fdc43)

* pr_labeler: re-architect triager script (#1882)

This commit reorganizes the issue/PR triager script and updates the
workflow to run more efficiently.

- Make the script a proper Python package instead of an unwieldy single
  file
- Use locked dependencies and UV to decrease workflow runtime to under
  10 seconds.

(cherry picked from commit 7138e42716)
(cherry picked from commit 1cf9f7917b)

---------

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-09-20 10:49:10 +01:00

52 lines
1.0 KiB
Plaintext

#
# This file is autogenerated by pip-compile with Python 3.10
# by the following command:
#
# pip-compile --allow-unsafe --output-file=tests/pr_labeler.txt --strip-extras tests/pr_labeler.in
#
certifi==2024.8.30
# via requests
cffi==1.17.1
# via
# cryptography
# pynacl
charset-normalizer==3.3.2
# via requests
click==8.1.7
# via typer-slim
codeowners==0.7.0
# via -r tests/pr_labeler.in
cryptography==43.0.1
# via pyjwt
deprecated==1.2.14
# via pygithub
idna==3.8
# via requests
jinja2==3.1.4
# via -r tests/pr_labeler.in
markupsafe==2.1.5
# via jinja2
pycparser==2.22
# via cffi
pygithub==2.4.0
# via -r tests/pr_labeler.in
pyjwt==2.9.0
# via pygithub
pynacl==1.5.0
# via pygithub
requests==2.32.3
# via pygithub
typer-slim==0.12.5
# via -r tests/pr_labeler.in
typing-extensions==4.12.2
# via
# codeowners
# pygithub
# typer-slim
urllib3==2.2.3
# via
# pygithub
# requests
wrapt==1.16.0
# via deprecated