You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/actions/next-repo-actions/src/bankrupt-issues.ts
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -6,19 +6,19 @@ async function main() {
6
6
7
7
constoctokit=getOctokit(process.env.GITHUB_TOKEN)
8
8
const{ owner, repo }=context.repo
9
-
constcreated=getInput('created')
10
-
constyear=created.slice(0,4)
9
+
constcreatedQuery=getInput('created')
10
+
constdateRange=createdQuery.split('..').join(' to ')
11
11
constbody=`
12
12
13
-
We are in the process of closing issues dating back to ${year} to improve our focus on the most relevant and actionable problems.
13
+
We are in the process of closing issues dating from ${dateRange} to improve our focus on the most relevant and actionable problems.
14
14
15
15
**_Why are we doing this?_**
16
16
17
17
Stale issues often lack recent updates and clear reproductions, making them difficult to address effectively. Our objective is to prioritize the most upvoted and actionable issues that have up-to-date reproductions, enabling us to resolve bugs more efficiently.
18
18
19
-
**_Why ${year} issues?_**
19
+
**_Why these issues?_**
20
20
21
-
Issues from ${year} are likely to be outdated and less relevant to the current state of the codebase. By closing these older stale issues, we can better focus our efforts on more recent and relevant problems, ensuring a more effective and streamlined workflow.
21
+
Issues dating from ${dateRange} are likely to be outdated and less relevant to the current state of the codebase. By closing these older stale issues, we can better focus our efforts on more recent and relevant problems, ensuring a more effective and streamlined workflow.
22
22
23
23
If your issue is still relevant, please reopen it using our [bug report template](https://github.com/vercel/next.js/issues/new?assignees=&labels=bug&projects=&template=1.bug_report.yml). Be sure to include any important context from the original issue in your new report.
24
24
@@ -30,13 +30,13 @@ The Next.js Team
30
30
31
31
letissues: number[]=[]
32
32
33
-
info(`created = ${created}`)
34
-
info(`year = ${year}`)
33
+
info(`created = ${createdQuery}`)
34
+
info(`date range = ${dateRange}`)
35
35
info(`body = ${body}`)
36
36
37
37
// try {
38
38
// const { data } = await octokit.rest.search.issuesAndPullRequests({
0 commit comments