Difference between revisions of "Github Actions"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
= Running actions manually = | = Running actions manually = | ||
| − | As a member of the Mudlet core dev team, visit the list of actions at https://github.com/Mudlet/Mudlet/actions. Once there, pick an action, and | + | As a member of the Mudlet core dev team, visit the list of actions at https://github.com/Mudlet/Mudlet/actions. Once there, pick an action, and use the <code>Run workflow</code> menu: |
| − | [[File:Running an action manually.png| | + | [[File:Running an action manually.png|frame|center]] |
| − | + | You can also select a particular branch you'd like the action to run against. Press the button and your workflow will start running. | |
Revision as of 09:23, 29 October 2020
What are they
They're automations that help Mudlet reduce administrative overhead. See Github's excellent overview for them.
Which have we got?
- Compile Mudlet in macOS. When: on every Git push.
- Update 3rdparty libraries used with Mudlet. When: every Friday night or manually. (This is: IRE Mapping script, Lua code formatter, character width algorithm, and our forks of edbee, sparkle-glue, dblsqd, qtkeychain. Note that fork updates don't check the origin repository but rather our forked version to ensure the main repo is up to date with it.)
- Update autocompletion information in Mudlet. When: every Friday night or manually.
- Update text available in Crowdin for translation. When: every Friday night or manually.
- Remove extra whitespace from commit. When: whenever called by typing
/wslintin a PR comment.
All of Mudlet's Github actions are available in the repository.
Running actions manually
As a member of the Mudlet core dev team, visit the list of actions at https://github.com/Mudlet/Mudlet/actions. Once there, pick an action, and use the Run workflow menu:
You can also select a particular branch you'd like the action to run against. Press the button and your workflow will start running.