rsnext/.github/workflows
Balázs Orbán 0f07cf5798
chore: verify missing/invalid/private reproduction links (#54724)
### What?

This PR adds a new action that verifies if the reproduction link is correct _after_ the issue has been created. If it is not, we close the issue and comment on it with the correct steps to take. Check out the [rendered comment here](https://github.com/balazsorban44/next.js/blob/chore/gh-invalid-link-checker/.github/actions/issue-validator/repro-link/invalid-link.md).

Additionally, this PR also does some refactoring to simplify our GitHub actions related to issues.

Tests:

Issue that was supposed to be closed:
 - https://github.com/balazsorban44/next.js/issues/48
   - Issue comment: https://github.com/balazsorban44/next.js/issues/48#issuecomment-1698836121 
   - Issue opened action: https://github.com/balazsorban44/next.js/actions/runs/6023209630
   - Issue labeled action: https://github.com/balazsorban44/next.js/actions/runs/6023209629

Issue that was not supposed to be closed (closed manually afterward):
 - https://github.com/balazsorban44/next.js/issues/49
   - Issue opened action: https://github.com/balazsorban44/next.js/actions/runs/6023214256
   - Issue labeled action: https://github.com/balazsorban44/next.js/actions/runs/6023214258


### Why?

Unfortunately, GitHub is currently missing the [functionality to require a valid reproduction link](https://github.com/orgs/community/discussions/10227) in issue templates. Even if that was supported, this PR adds functionality that could not be covered with a regex validation. Namely, we check if the reproduction is a private repo or not, and potentially could also check the structure to see if it's an actual Next.js project.

### How?

If the link is not in the expected section, not a GitHub, CodeSandbox, or Replay.io link, or does not return an OK response (eg.: private repo/sandbox), the issue is closed/commented.

Related:
- https://github.com/orgs/community/discussions/4629
- https://github.com/orgs/community/discussions/10227

Co-authored-by: Steven <229881+styfle@users.noreply.github.com>
2023-08-30 17:40:57 +00:00
..
build_and_deploy.yml Consider cargo config in granular cache key (#54700) 2023-08-28 22:29:28 -07:00
build_and_test.yml Update runner labels (#53925) 2023-08-11 21:05:11 +00:00
build_reusable.yml Consider cargo config in granular cache key (#54700) 2023-08-28 22:29:28 -07:00
cancel.yml chore(ci): bump cancel-workflow-action@0.11.0 (#54246) 2023-08-18 20:29:57 +00:00
issue_lock.yml chore: update lock bot wording (#54099) 2023-08-16 09:05:04 +00:00
issue_on_comment.yml chore: add GitHub Action to manage "+1" comments (#52866) 2023-07-20 09:34:29 +00:00
issue_stale.yml chore: add "please simplify reproduction" comment (#52631) 2023-07-14 23:30:42 +00:00
issue_validator.yml chore: verify missing/invalid/private reproduction links (#54724) 2023-08-30 17:40:57 +00:00
notify_release.yml ci(workflow): notify new releases to vercel/turbo via repo_dispatch (#45201) 2023-01-24 16:41:28 -08:00
pull_request_approved.yml chore: skip CI run on forks (#54219) 2023-08-18 17:40:44 +00:00
pull_request_stats.yml Update release stats install/build executing (#54576) 2023-08-25 12:45:58 -07:00
test_examples.yml [chore] Upgrade playwright to 1.35.1 (#53875) 2023-08-11 23:25:01 +00:00
trigger_release.yml chore: update to pnpm@8.6.11 (#50923) 2023-08-04 19:40:20 +00:00
update_fonts_data.yml Update env variable for fonts data workflow (#53701) 2023-08-07 22:07:50 +00:00