Run the gate on Forgejo Actions #491
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
spec
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#495 Build the image and deploy previews and production from Forgejo
amaurycoudr/chess-project
#496 Schedule the audit, the production backup and Renovate on Forgejo
amaurycoudr/chess-project
#498 Freeze GitLab: turn off previews and deploys, close open merge requests
amaurycoudr/chess-project
Reference
amaurycoudr/chess-project#491
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent
#489
What to build
A pull request's gate runs on Forgejo Actions:
checks,front-testande2e, ported from the GitHub Actions workflows removed in87f541fd, with the GitLab-era changes kept (shared Turbo volume, Node and Playwright images, Postgres and Mailpit services, heap and concurrency limits). A new push cancels the run it supersedes through workflow-levelconcurrency. A docs-only pull request ends the app jobs at once. A push tomainskips the gate when the pull request that holds its commit already passed on it, by asking Forgejo's API. The check names are stable, so branch protection can require them. The workflows merge on GitLab, which ignores them.Seam: a Forgejo Actions run (spec
## Seams).Acceptance criteria
checks,front-testande2erun on a pull request and report one status each, under names branch protection can require.docs/-only pull request ends the app jobs early and still reports green.mainwhose pull request passed on the same commit skips the three jobs; any API error lets them run.mentioned in issue #495
mentioned in issue #496
mentioned in issue #498
marked this issue as related to #489
marked this issue as related to #495
marked this issue as related to #496
marked this issue as related to #498
mentioned in merge request !568
mentioned in commit
0bd1f48ed3mentioned in commit
640dc222f3mentioned in commit
565582c053mentioned in commit
806ed99c94