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...")
 
(→‎Running actions manually: the page gives visual feedback now, so 'nothing will happen' no longer applies)
(3 intermediate revisions by 2 users not shown)
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. 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 autocompletion information in Mudlet. When: every Friday night or manually.
# Update text available in Crowdin for translation. When: every Friday night or manually.
+
# Update [[Translating_Mudlet|text available in Crowdin]] for translation. When: every Friday night or manually.
 
# Remove extra whitespace from commit. When: whenever called by typing <code>/wslint</code> in a PR comment.
 
# Remove extra whitespace from commit. When: whenever called by typing <code>/wslint</code> in a PR comment.
  
  
 
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.
Line 15: Line 16:
 
[[File:Running an action manually.png|thumb|left]]
 
[[File:Running an action manually.png|thumb|left]]
  
While nothing might seem to happen, this is normal - go to [https://github.com/Mudlet/Mudlet/actions Mudlet's actions overview] and you'll see your action running.
+
After running an action, you can go to [https://github.com/Mudlet/Mudlet/actions Mudlet's actions overview] and you'll see your action running.

Revision as of 09:55, 17 May 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. 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.)
  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

After running an action, you can go to Mudlet's actions overview and you'll see your action running.