rsnext/.github
Zack Tanner fb9773f82b
set persist-credentials: false during release workflow (#62905)
This ensures the release bot token is used when publishing the release. 

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->


Closes NEXT-2717
2024-03-05 12:43:22 -08:00
..
actions Fix handling for getting latest stable tag (#62858) 2024-03-04 19:41:30 -08:00
comments chore: add resolved label (#61416) 2024-01-31 02:50:23 +01:00
DISCUSSION_TEMPLATE chore: improve repo templates (#46629) 2023-03-01 09:25:51 -08:00
ISSUE_TEMPLATE chore: indicate staleness more prominently in next info output (#60376) 2024-01-19 18:36:19 +01:00
workflows set persist-credentials: false during release workflow (#62905) 2024-03-05 12:43:22 -08:00
CODEOWNERS chore: add new codeowners for cli refactor (#62749) 2024-03-01 15:13:19 -08:00
labeler.json chore: fix core team members (#60900) 2024-01-19 10:19:32 -08:00
pnpm-lock.yaml chore: add pull_request_popular workflow (#61760) 2024-02-07 14:59:46 -08:00
pnpm-workspace.yaml chore(ci): add pnpm workspace for github actions (#52976) 2023-07-21 14:29:31 +00:00
pull_request_template.md Update pull_request_template.md (#55098) 2023-09-08 00:19:49 +00:00