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

github-actions bot also triggers when build step failed #1840

Closed
8 of 10 tasks
Shinigami92 opened this issue Feb 14, 2023 · 4 comments · Fixed by #3039
Closed
8 of 10 tasks

github-actions bot also triggers when build step failed #1840

Shinigami92 opened this issue Feb 14, 2023 · 4 comments · Fixed by #3039
Labels
c: bug Something isn't working c: infra Changes to our infrastructure or project setup p: 1-normal Nothing urgent s: accepted Accepted feature / Confirmed bug
Milestone

Comments

@Shinigami92
Copy link
Member

Pre-Checks

Describe the bug

This is an infra bug in our CI

The github-actions bot also triggers when build step failed
Then it suggest to run pnpm run generate:locales, pnpm run generate:api-docs, and pnpm run test -u
But these are totally wrong suggestions as the build step already failed

I see two solutions:

  1. Do not print the github-actions bot when the build or anything before that already failed (my preferred solution)
  2. Listing all comments that needs to be done to fix the CI (this could get very spammy and unnecessary verbose)

Minimal reproduction code

No response

Additional Context

image

Environment Info

-

Which module system do you use?

  • CJS
  • ESM

Used Package Manager

pnpm

@Shinigami92 Shinigami92 added c: bug Something isn't working s: pending triage Pending Triage labels Feb 14, 2023
@xDivisionByZerox xDivisionByZerox added p: 1-normal Nothing urgent c: infra Changes to our infrastructure or project setup and removed s: pending triage Pending Triage labels Feb 16, 2023
@xDivisionByZerox
Copy link
Member

This will be solved by #1846 as well

@ST-DDT ST-DDT added the s: accepted Accepted feature / Confirmed bug label Feb 16, 2023
@ST-DDT ST-DDT moved this to Awaiting Review in Faker Roadmap Feb 16, 2023
@ST-DDT
Copy link
Member

ST-DDT commented Feb 16, 2023

This will be solved by #1846 as well

🤔 We either have to change the wording to not explicitly refer to uncommitted changes
or have to change the conditions for firing the message.

@xDivisionByZerox
Copy link
Member

@ST-DDT can this be considered fixed and closed?

@ST-DDT
Copy link
Member

ST-DDT commented Nov 26, 2023

No, the message still refers to uncommited changes, but also triggers for test failures and other stuff IIRC.
(Also the message only triggers for members and not external contributors.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: bug Something isn't working c: infra Changes to our infrastructure or project setup p: 1-normal Nothing urgent s: accepted Accepted feature / Confirmed bug
Projects
No open projects
Status: Awaiting Review
Development

Successfully merging a pull request may close this issue.

3 participants