rsnext/scripts/automated-update-workflow.js

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

96 lines
2.3 KiB
JavaScript
Raw Normal View History

const { promisify } = require('util')
const { Octokit } = require('octokit')
const { exec: execOriginal } = require('child_process')
const exec = promisify(execOriginal)
const {
GITHUB_TOKEN = '',
SCRIPT = '',
BRANCH_NAME = 'unknown',
PR_TITLE = 'Automated update',
PR_BODY = '',
} = process.env
if (!GITHUB_TOKEN) {
console.log('missing GITHUB_TOKEN env')
process.exit(1)
}
if (!SCRIPT) {
console.log('missing SCRIPT env')
process.exit(1)
}
async function main() {
const octokit = new Octokit({ auth: GITHUB_TOKEN })
const branchName = `update/${BRANCH_NAME}-${Date.now()}`
await exec(`node ${SCRIPT}`)
await exec(`git config user.name "vercel-release-bot"`)
await exec(`git config user.email "infra+release@vercel.com"`)
await exec(`git checkout -b ${branchName}`)
await exec(`git add -A`)
await exec(`git commit --message ${branchName}`)
const changesResult = await exec(`git diff HEAD~ --name-only`)
const changedFiles = changesResult.stdout
.split('\n')
.filter((line) => line.trim())
if (changedFiles.length === 0) {
console.log('No files changed skipping.')
return
}
await exec(`git push origin ${branchName}`)
const repo = 'next.js'
const owner = 'vercel'
const { data: pullRequests } = await octokit.rest.pulls.list({
owner,
repo,
state: 'open',
sort: 'created',
direction: 'desc',
per_page: 100,
})
const pullRequest = await octokit.rest.pulls.create({
owner,
repo,
head: branchName,
base: 'canary',
title: PR_TITLE,
body: PR_BODY,
})
console.log('Created pull request', pullRequest.url)
const previousPullRequests = pullRequests.filter(({ title, user }) => {
return title.includes(PR_TITLE) && user.login === 'vercel-release-bot'
})
if (previousPullRequests.length) {
for await (const previousPullRequest of previousPullRequests) {
console.log(
`Closing previous pull request: ${previousPullRequest.html_url}`
)
await octokit.rest.pulls.update({
owner,
repo,
pull_number: previousPullRequest.number,
state: 'closed',
})
}
}
}
Ensure automated-update-workflow fails on errors (#63807) ## What? Ensure that test runs like this one fail: https://github.com/vercel/next.js/actions/runs/8463659474/job/23186935591 <!-- 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-2953
2024-03-28 12:29:45 +01:00
main().catch((err) => {
console.error(err)
// Ensure the process exists with a non-zero exit code so that the workflow fails
process.exit(1)
})