Skip to content
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

Merged
merged 3 commits into from
Apr 29, 2022
Merged

chore: fix release issue #447

merged 3 commits into from
Apr 29, 2022

Conversation

shortcuts
Copy link
Member

🧭 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

@netlify
Copy link

netlify bot commented Apr 28, 2022

Deploy Preview for api-clients-automation canceled.

Name Link
🔨 Latest commit 4cdcbfa
🔍 Latest deploy log https://app.netlify.com/sites/api-clients-automation/deploys/626aad108293920009f5963f

Comment on lines 204 to 209
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;
}
Copy link
Member Author

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oki that make sense!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

restored here: 4cdcbfa

@algolia-bot
Copy link
Collaborator

algolia-bot commented Apr 28, 2022

✗ The generated branch has been deleted.

If the PR has been merged, you can check the generated code on the main branch.

@shortcuts shortcuts assigned shortcuts and unassigned eunjae-lee Apr 28, 2022
<ul>
${commitsWithUnknownLanguageScope.map((commit) => `<li>${commit}</li>`)}
</ul>`;
return `</p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
return `</p>
return `<p></p>

it was that actually, to make a space. (you need to update the tests as well)

Copy link
Member Author

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

Copy link
Collaborator

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> ?

@shortcuts shortcuts enabled auto-merge (squash) April 28, 2022 15:40
@shortcuts shortcuts requested review from eunjae-lee and millotp April 29, 2022 08:20
Copy link
Collaborator

@millotp millotp left a 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>
Copy link
Collaborator

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> ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants