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.

Sign up for GitHub

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

Jump to bottom

Migrate to GitHub actions #20

Open
matthiasrohmer opened this issue Sep 23, 2022 · 0 comments
Open

Migrate to GitHub actions #20

matthiasrohmer opened this issue Sep 23, 2022 · 0 comments

Comments

@matthiasrohmer
Copy link
Member

I think we could save ourselves some sanity by migrating this to GitHub actions. The main motivation is getting rid of using Glitch as a sort of production backend but also:

  • being able to trace runs via the GitHub actions UI (why did a run fail, when did it run, ...)
  • making use of action annotations to visually connect Markdown lint errors to the PR code. This will make reviews easier
  • being able to use existing actions like Sticky Pull Request comment to reduce noise
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@matthiasrohmer