Difference between revisions of "Github Actions"

From Mudlet
Jump to navigation Jump to search
(Created page with "= What are they = They're automations that help Mudlet reduce administrative overhead. See Github's [https://github.com/features/actions excellent overview] for them. = Which...")
 
Line 3: Line 3:
 
= Which have we got? =
 
= Which have we got? =
 
# Compile Mudlet in macOS. When: on every Git push.
 
# Compile Mudlet in macOS. When: on every Git push.
# Update 3rdparty libraries used with Mudlet. This is: IRE Mapping script, Lua code formatter, character width algorithm, and our forks of edbee, sparkle-glue, dblsqd, qtkeychain. Note that forks updates don't check the origin repository but rather our forked version to ensure the main repo is up to date with it. When: every Friday night or manually.
+
# Update 3rdparty libraries used with Mudlet. 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. When: every Friday night or manually.
 
# Update autocompletion information in Mudlet. When: every Friday night or manually.
 
# Update autocompletion information in Mudlet. When: every Friday night or manually.
 
# Update text available in Crowdin for translation. When: every Friday night or manually.
 
# Update text available in Crowdin for translation. When: every Friday night or manually.
Line 10: Line 10:
  
 
All of Mudlet's Github actions are available [https://github.com/Mudlet/Mudlet/tree/development/.github/workflows in the repository].
 
All of Mudlet's Github actions are available [https://github.com/Mudlet/Mudlet/tree/development/.github/workflows in the repository].
 +
 
= Running actions manually =
 
= Running actions manually =
 
As a member of the Mudlet core dev team, visit the panel available at https://www.actionspanel.app/app/Mudlet/Mudlet. Once there, you can hit the green button on an action to run it manually.
 
As a member of the Mudlet core dev team, visit the panel available at https://www.actionspanel.app/app/Mudlet/Mudlet. Once there, you can hit the green button on an action to run it manually.

Revision as of 06:12, 20 April 2020

What are they

They're automations that help Mudlet reduce administrative overhead. See Github's excellent overview for them.

Which have we got?

  1. Compile Mudlet in macOS. When: on every Git push.
  2. Update 3rdparty libraries used with Mudlet. 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. When: every Friday night or manually.
  3. Update autocompletion information in Mudlet. When: every Friday night or manually.
  4. Update text available in Crowdin for translation. When: every Friday night or manually.
  5. Remove extra whitespace from commit. When: whenever called by typing /wslint in 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 panel available at https://www.actionspanel.app/app/Mudlet/Mudlet. Once there, you can hit the green button on an action to run it manually.

Running an action manually.png

While nothing might seem to happen, this is normal - go to Mudlet's actions overview and you'll see your action running.