-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: fix release issue #447
Conversation
✅ Deploy Preview for api-clients-automation canceled.
|
scripts/release/process-release.ts
Outdated
if (!(await isAuthorizedRelease())) { | ||
throw new Error( | ||
console.log( | ||
'The issue was not approved.\nA team member must leave a comment "approved" in the release issue.' | ||
); | ||
return; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was making the CI fail, I think it's enough but let me know if it was intended @eunjae-lee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah it is intended. If we decide not to release an issue, then we can just close it, which ends up failing on the CI, but we can still ignore it.
On the other hand, someone leaves a comment with a typo like aproved
, then it should explicitly fail, so that we know.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oki that make sense!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
restored here: 4cdcbfa
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
<ul> | ||
${commitsWithUnknownLanguageScope.map((commit) => `<li>${commit}</li>`)} | ||
</ul>`; | ||
return `</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
return `</p> | |
return `<p></p> |
it was that actually, to make a space. (you need to update the tests as well)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't you think it look nice on the preview? #446
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when do you open the <p>
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks nice on #446 so imma approve
<ul> | ||
${commitsWithUnknownLanguageScope.map((commit) => `<li>${commit}</li>`)} | ||
</ul>`; | ||
return `</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when do you open the <p>
?
🧭 What and Why
🎟 JIRA Ticket: -
Changes included:
The format of the release issue was a bit broken (see #445), so I've updated it #446
🧪 Test
Before: #445
After: #446