archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
21428 commits 5 branches 0 tags 1.9 GiB
Commit graph

13 commits

Author SHA1 Message Date
Sam Ko
af93aafc95
chore(github-workflow): update bankrupt-issues (#67023) 
## Why?

Add slack message after bankrupting issues.
 2024-06-19 13:53:41 +00:00
Sam Ko
32c2795e54
chore(github-workflow): add bankrupt issues workflow (#66383) 
## Why?

Add an empty bankrupt issues workflow so I can start testing the GitHub
Action.

## Changes

- Rename `.github/actions/next-repo-info` →
`.github/actions/next-repo-actions`
- Add `issue_bankrupt.yml` GitHub workflow
 2024-06-05 11:33:56 -07:00
Sam Ko
b04cc939e4
chore(github-workflow): update popular workflows cron time, fix undef… (#65172) 
## Why?

- Fix total reactions from being undefined, also switch it to ↑ instead
of 👍🏼
- Update cron times to be 3 hours earlier (better suit EU timezone)

Closes NEXT-3253
 2024-04-29 19:34:36 +00:00
Balázs Orbán
a6dfe82385
chore: notify on popular feature requests (#64877) 2024-04-25 12:05:20 +02:00
Sam Ko
f8aa7f3af8
chore: add pull_request_popular workflow (#61760) 
## Description

Add a GitHub Workflow that notifies us (internally) about the top 15
:pr:s (most reacted) in the last 90
days.

Closes NEXT-2387
 2024-02-07 14:59:46 -08:00
Sam Ko
7b73f1137b
chore: add issue_popular workflow (#60543) 
## Description
Add a new GitHub workflow that outputs the top 15 :github2: issues (most reactions) in
the last month.

Closes NEXT-2071
 2024-01-11 18:27:47 -08:00
Leah
15215d4c96
ci: report daily turbo integration test results from this repo (#58965) 
### What?

A follow up for #58267 and #58394.

We no longer need the git branch for history it's stored in datadog now
and we also decided that we no longer need slack reporting.


Closes PACK-2039

---------

Co-authored-by: Tim Neutkens <tim@timneutkens.nl>
 2023-12-04 16:18:42 +01:00
Will Binns-Smith
d73b8366af
Use node:fs instead of fs-extra in .github/actions (#56536) 
Test Plan: Stats for this PR?


Closes WEB-1730
 2023-10-11 00:52:55 +00:00
Balázs Orbán
d5c35a1bbb
chore: replace issue triaing actions with nissuer (#55525) 
### What?

Moving maintenance to a separate repository.

### Why?

I want to make these actions reusable in other projects as they seem to work well in the Next.js repository.

### How?

The code is moved to https://github.com/balazsorban44/nissuer

I tested it on my fork, and all the following functionality is preserved: https://github.com/balazsorban44/next.js/issues/56

- [x] Close/lock/comment without a valid reproduction link
- [x] Minimize "+1"
- [x] Add labels based on user selection
- [x] Add comment based on the maintainer's label (eg.: "please add a complete reproduction")
 2023-09-19 11:11:00 +00:00
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
Balázs Orbán
633b553842
chore: hide "same on new version" without link (#54048) 
Chat with @timneutkens

- Lock closed issues after 14 days of inactivity
- Hide comments "still happening" without a link we can verify
 2023-08-15 09:44:07 +00:00
Balázs Orbán
3a86b30d68
chore: add GH action to notify about pending PRs (#53541) 
Send us daily notifications when approved and open PRs haven't been merged yet. See [Slack thread](https://vercel.slack.com/archives/C04DUD7EB1B/p1690610821861229) for more context.

It queries: https://github.com/search?q=repo%3Avercel%2Fnext.js%20is%3Apr%20is%3Aopen%20review%3Aapproved%20&type=pullrequests for the number of PRs, then posts a message with a link to https://github.com/vercel/next.js/pulls?q=is%3Apr+is%3Aopen+review%3Aapproved
 2023-08-03 21:40:28 +00:00
Steven
032e8d0eb0
chore(ci): add pnpm workspace for github actions (#52976) 
This creates a monorepo for each github action and ensures they all use pnpm.

You can install and build all with the following:

```
cd .github
pnpm i
pnpm -r build
```
 2023-07-21 14:29:31 +00:00