Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Celebrate your progress with Github Actions

Celebrate your progress with Github Actions

Action! Celebrate!

This talk was made for the PyLadies International Women's Day event 2021. It demonstrates how to use Github actions to remind yourself and others to celebrate your progress and achievements.

Jessica Greene

March 08, 2021
Tweet

More Decks by Jessica Greene

Other Decks in Programming

Transcript

  1. “The more you praise and celebrate your life, the more

    there is in life to celebrate.” —Oprah Winfrey
  2. GITHUB ACTIONS! GitHub Actions provide a way to automate your

    software development workflows on GitHub. This includes traditional CI/CD tasks such as running test suites, building applications and publishing packages.
  3. GITHUB ACTIONS! But it also includes automated greetings for new

    contributors, labelling pull requests based on the files changed, or even creating cron jobs to perform scheduled tasks.
  4. Individual tasks; you can write your own actions or use

    an action someone else created A tale of Two parts Workflows Github Actions Automated processes that run on your repository; workflows can have many GitHub actions
  5. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  6. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  7. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  8. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  9. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  10. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  11. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  12. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  13. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  14. 02 Inputs (optional) specify data your action expects 3 main

    components of an action: 03 Outputs (optional) declare data that an action sets 01 Runs (required) configures the path to the actions code and the application used to execute the code (Docker/ Javascript/ shell script)
  15. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  16. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  17. Putting it together Tweet My appreciation The idea is to

    have a workflow which when someone makes a pull request uses an action that sends out a Tweet to celebrate that person's work!!
  18. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  19. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  20. CREDITS: This presentation template was created by Slidesgo, including icons

    by Flaticon, and infographics & images by Freepik THANKS! Do you have any questions? @sleepypioneer www.github.com/sleepypioneer
  21. The event that triggers the workflow The jobs that make

    the workflow The machine each job should run The tasks each job should run 01. on 02. jobs 03. runs-on 04. steps The command the step should run 05. run
  22. DON’T FORGET to celebrate • https://github.com/sleepypioneer/pyladies_IWD • https://github.com/sleepypioneer/actions_to_celebrate • https://github.com/features/actions

    • https://github.com/marketplace • Tweepy: https://docs.tweepy.org/en/latest/index.html • PyGithub: https://pygithub.readthedocs.io/en/latest/index.html