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 Ideas Thread #808

Closed
arschles opened this issue Oct 23, 2018 · 8 comments
Closed

GitHub Actions Ideas Thread #808

arschles opened this issue Oct 23, 2018 · 8 comments
Labels
ci/cd Work to do to improve our CI/CD system community Something to improve the Athens community

Comments

@arschles
Copy link
Member

Personally I can't wait until we can use GitHub Actions on this project! My TL;DR on actions: a hosted (by GitHub) system where you can run any code (in Docker containers) to respond to any webhook that the repo fires

We don't have access to actions on this repo yet, but I have some ideas on what we can do with them when we do. They're super flexible and I bet we as a community have ALL KINDS of ideas what we can do with them.

Let's keep our ideas in here so we can go and do them when the time comes!

@arschles
Copy link
Member Author

Top of my head ideas:

  • We can obviously run our tests in an action, and replace Travis-CI (we probably don't need to do this, but it'd be fun methinks)
  • We could deploy an Athens server on each commit to a PR, and tear it down after that PR is closed
  • We could crawl the docs site to look for dead links
  • We could publish a tweet to the @gomodsio Twitter account when we publish a new GitHub release
  • We could build changelogs for new GH releases automatically from commit messages

@arschles arschles added community Something to improve the Athens community ci/cd Work to do to improve our CI/CD system labels Oct 23, 2018
@chriscoffee
Copy link
Member

chriscoffee commented Oct 24, 2018

  • Check if there's any diff in the docs and deploy only if changes been made.
  • Spellcheck/grammar check of docs.
  • Probe endpoints on previews
  • Run extended tests like checking the Azure Storage backend with Azurite or similar.

We could publish a tweet to the @gomodsio Twitter account when we publish a new GitHub release

  • This could also include what's been changed with the changelog action you mention below that.

@arschles
Copy link
Member Author

@chriscoffee do you have a link to Azurite?

@marpio
Copy link
Member

marpio commented Oct 24, 2018

@chriscoffee
Copy link
Member

chriscoffee commented Oct 24, 2018

Thanks @marpio I was afk sorry! 👍

@michalpristas
Copy link
Member

@arschles we talked about Release notes yesterday. so I was thinking maybe we can automate it with actions?
with each tag, we can publish a release notes with a list of Issues (not PRs as PR may fix a typo or another very minor thing)

@arschles
Copy link
Member Author

This repository now has actions enabled. I'm going to open a new issue to add some actions alongside our drone / appveyor setup and see how it goes

@arschles
Copy link
Member Author

Closing in favor of #1460

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci/cd Work to do to improve our CI/CD system community Something to improve the Athens community
Projects
None yet
Development

No branches or pull requests

4 participants