Conversation
|
Please review this PR. Thank you. |
| { | ||
| "name": "stale-action", | ||
| "version": "7.0.0", | ||
| "version": "8.0.0", |
There was a problem hiding this comment.
| "version": "8.0.0", | |
| "version": "9.0.0", |
|
|
||
| type state_reason_type = | ||
| | 'completed' | ||
| | 'reopened' | ||
| | 'not_planned' | ||
| | null | ||
| | undefined; |
There was a problem hiding this comment.
What was the reason for adding this type?
There was a problem hiding this comment.
While I was running npm run test few test and test suites are failed for the code
state_reason: this.options.closeIssueReason || undefined for that I have intialized status_reason and updated the line of code. Now I have rechecked the code and updated the line. All tests passed with same line now.
| issue_number: issue.number, | ||
| state: 'closed', | ||
| state_reason: this.options.closeIssueReason || undefined | ||
| state_reason: this.options.closeIssueReason as state_reason_type |
There was a problem hiding this comment.
In this code update, you changed the logic. The this.options.closeIssueReason is typed as a string. The code state_reason: this.options.closeIssueReason || undefined means that if the this.options.closeIssueReason is an empty string we assign state_reason with undefined.
In your version of code this logic is changed. If the this.options.closeIssueReason is an empty string you assign state_reason with an empty string. What is the reason for that?
There was a problem hiding this comment.
To resolve the failed tests for that particular line I have added the change and I missed the logic that I am assigning the empty string. Now I have updated the logic. Thank you for the clarification.
Bumps actions/stale from 8 to 9. Release notes Sourced from actions/stale's releases. v9.0.0 Breaking Changes Action is now stateful: If the action ends because of operations-per-run then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). The state is reset when all the issues are processed. This should be considered for scheduling workflow runs. Version 9 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20. What Else Changed Performance optimization that removes unnecessary API calls by @dsame #1033 fixes #792 Logs displaying current github API rate limit by @dsame #1032 addresses #1029 For more information, please read the action documentation and its section about statefulness New Contributors @jmeridth made their first contribution in actions/stale#984 @nikolai-laevskii made their first contribution in actions/stale#1020 @dusan-trickovic made their first contribution in actions/stale#1056 @aparnajyothi-y made their first contribution in actions/stale#1110 Full Changelog: actions/stale@v8...v9.0.0
Bumps actions/stale from 8 to 9. Release notes Sourced from actions/stale's releases. v9.0.0 Breaking Changes Action is now stateful: If the action ends because of operations-per-run then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). The state is reset when all the issues are processed. This should be considered for scheduling workflow runs. Version 9 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20. What Else Changed Performance optimization that removes unnecessary API calls by @dsame #1033 fixes #792 Logs displaying current github API rate limit by @dsame #1032 addresses #1029 For more information, please read the action documentation and its section about statefulness New Contributors @jmeridth made their first contribution in actions/stale#984 @nikolai-laevskii made their first contribution in actions/stale#1020 @dusan-trickovic made their first contribution in actions/stale#1056 @aparnajyothi-y made their first contribution in actions/stale#1110 Full Changelog: actions/stale@v8...v9.0.0
Bumps actions/stale from 8 to 9. Release notes Sourced from actions/stale's releases. v9.0.0 Breaking Changes Action is now stateful: If the action ends because of operations-per-run then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). The state is reset when all the issues are processed. This should be considered for scheduling workflow runs. Version 9 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20. What Else Changed Performance optimization that removes unnecessary API calls by @dsame #1033 fixes #792 Logs displaying current github API rate limit by @dsame #1032 addresses #1029 For more information, please read the action documentation and its section about statefulness New Contributors @jmeridth made their first contribution in actions/stale#984 @nikolai-laevskii made their first contribution in actions/stale#1020 @dusan-trickovic made their first contribution in actions/stale#1056 @aparnajyothi-y made their first contribution in actions/stale#1110 Full Changelog: actions/stale@v8...v9.0.0
Bumps actions/stale from 8 to 9. Release notes Sourced from actions/stale's releases. v9.0.0 Breaking Changes Action is now stateful: If the action ends because of operations-per-run then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). The state is reset when all the issues are processed. This should be considered for scheduling workflow runs. Version 9 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20. What Else Changed Performance optimization that removes unnecessary API calls by @dsame #1033 fixes #792 Logs displaying current github API rate limit by @dsame #1032 addresses #1029 For more information, please read the action documentation and its section about statefulness New Contributors @jmeridth made their first contribution in actions/stale#984 @nikolai-laevskii made their first contribution in actions/stale#1020 @dusan-trickovic made their first contribution in actions/stale#1056 @aparnajyothi-y made their first contribution in actions/stale#1110 Full Changelog: actions/stale@v8...v9.0.0
Description:
Code changes for Node version upgrade to 20
Related issue:
Feature request
Check list: