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

Refactor commit status for Actions jobs (#23786) #24060

Merged
merged 2 commits into from
Apr 12, 2023

Conversation

denyskon
Copy link
Member

@denyskon denyskon commented Apr 11, 2023

Backport #23786

Refactor commit status for Actions jobs (#23786)

Before:
xnip_230329_163852 After:
xnip_230329_163358

Highlights:

  • Treat StatusSkipped as CommitStatusSuccess instead of CommitStatusFailure, so it fixed [actions] Skipped jobs are displayed as failed #23599.
  • Use the bot user gitea-actions instead of the trigger as the creator of commit status.
  • New format <run_name> / <job_name> / (<event>) for the context of commit status to avoid conflicts.
  • Add descriptions for commit status.
  • Add the missing calls to CreateCommitStatus.
  • Refactor CreateCommitStatus to make it easier to use.

Refactor commit status for Actions jobs (go-gitea#23786)

Before:
<img width="353" alt="xnip_230329_163852"
src="https://user-images.githubusercontent.com/9418365/228479807-424452df-10fa-45cf-ae4b-09939c0ed54c.png">
After:
<img width="508" alt="xnip_230329_163358"
src="https://user-images.githubusercontent.com/9418365/228479923-537b54fe-9564-4105-a068-bcc75fa2a7ea.png">

Highlights:
- Treat `StatusSkipped` as `CommitStatusSuccess` instead of
`CommitStatusFailure`, so it fixed go-gitea#23599.
- Use the bot user `gitea-actions` instead of the trigger as the creator
of commit status.
- New format `<run_name> / <job_name> / (<event>)` for the context of
commit status to avoid conflicts.
- Add descriptions for commit status.
- Add the missing calls to `CreateCommitStatus`.
- Refactor `CreateCommitStatus` to make it easier to use.
@delvh delvh added type/bug type/enhancement An improvement of existing functionality topic/gitea-actions related to the actions of Gitea labels Apr 11, 2023
@delvh delvh added this to the 1.19.1 milestone Apr 11, 2023
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Apr 11, 2023
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Apr 12, 2023
@techknowlogick techknowlogick enabled auto-merge (squash) April 12, 2023 02:06
@techknowlogick techknowlogick added the reviewed/wait-merge This pull request is part of the merge queue. It will be merged soon. label Apr 12, 2023
@techknowlogick
Copy link
Member

🤖 🎺

@wolfogre
Copy link
Member

Thanks! And sorry I overlooked this. 😂

@techknowlogick techknowlogick merged commit 29724f3 into go-gitea:release/v1.19 Apr 12, 2023
@GiteaBot GiteaBot removed the reviewed/wait-merge This pull request is part of the merge queue. It will be merged soon. label Apr 12, 2023
@denyskon denyskon deleted the backport/23786 branch April 12, 2023 03:32
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Jul 31, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. topic/gitea-actions related to the actions of Gitea type/bug type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants