mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-13 20:29:35 +00:00
32f987fc8c
Many GitHub Actions workflows currently trigger on user forks, leading to unnecessary CI resource consumption, unwanted bot behavior, and inevitable failures. This commit restricts these specific workflows to only run on the primary `containers/podman` repository. The restricted workflows fall into two main categories: 1. Require Custom Upstream Secrets: Workflows like `release`, `mac-pkg`, `cherry-pick`, and `dev-bump` rely on secrets (e.g., Apple/Azure certs, PODMANBOT_TOKEN, ACTION_MAIL_*) that are unavailable in forks. 2. Manage Upstream Tracker State: Workflows like `assign`, `stale`, and `labeler` are intended strictly for managing the primary project's issues and PRs. Running them on personal forks creates unwanted noise. Additionally, refactored several complex `if` conditions using YAML multi-line strings (`|`) to maintain and improve readability. Signed-off-by: Byounguk Lee <nimdrak@gmail.com>
33 lines
1.1 KiB
YAML
33 lines
1.1 KiB
YAML
name: Needs info labeler
|
|
on:
|
|
issues:
|
|
types:
|
|
- labeled
|
|
|
|
permissions: {}
|
|
|
|
jobs:
|
|
add-comment:
|
|
if: |
|
|
github.event.label.name == 'needs-info' &&
|
|
github.repository == 'podman-container-tools/podman'
|
|
runs-on: ubuntu-latest
|
|
permissions:
|
|
issues: write
|
|
steps:
|
|
- name: Add comment
|
|
run: gh issue comment "$NUMBER" --body "$BODY"
|
|
env:
|
|
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
GH_REPO: ${{ github.repository }}
|
|
NUMBER: ${{ github.event.issue.number }}
|
|
BODY: |
|
|
A reviewer has determined we need more information to understand the reported issue. A comment on what is missing should be provided. Be certain you:
|
|
|
|
* provide an exact reproducer where possible
|
|
* verify you have provided all relevant information - minimum is `podman info`
|
|
* answer any follow up questions
|
|
|
|
If no response to the `needs-info` is provided in 30 days, this issue may be closed by our stale bot.
|
|
|
|
For more information on reporting issues on this repository, consult our [issue guide](ISSUE.md).
|