github actions | notes | kipras melnikovas

github actions

words:	2 + 594 = 596
last update:

#public
#github

Linked Mentions (12 in 10 pages)

October 24th, 2021 (1)

{{[[TODO]]}} perhaps consider like separate steps' output (like #[[github actions]]), indexed again by a function (object) reference as key(s)

November 29th, 2021 (1)

#[[github actions]] runner setup
- https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-20-04
- ```shell sudo apt install build-essential libcurl4-gnutls-dev libxml2-dev libssl-dev```
- https://askubuntu.com/a/923317
- ```shell apt install firefox```
- {{[[TODO]]}} still failing...
- if manually copying graph:
  - can proceed
  - https://classic.yarnpkg.com/lang/en/docs/install/#[[(hidden) G97ohL3l8]]debian-stable
    - install nvm
    - then
      - ```javascript nvm install 12 nvm use 12 # DO NOT ($PATH setup sucks) # npm i -g yarn # DO: sudo apt update && sudo apt install --no-install-recommends yarn```

November 30th, 2021 (1)

oh my god [[github actions]] SUCK
- YET AGAIN
- ofc not everything is bad abt them. & they'll improve eventually. nevertheless

December 2nd, 2021 (1)

{{[[TODO]]}} or maybe finally fix whatever's broken in [[github actions]] lol

December 10th, 2021 (1)

{{[[TODO]]}} as for security, i keep thinking about: should i include the security info in the default setup when explaining how to use the plugin in e.g. [[github actions]], or should i put it afterwards
- i think the defaults matter. and so i should definitely put it in the default setup, because that's what everyone's gonna do.
- the easiest thing to do, for starters, is to fork the repository and use the fork, instead of the main repo, as the source of the plugin(s)
  - updating is very easy. `fetch upstream` button available in [[github]] right next to the latest commit's info
  - {{[[TODO]]}} the repo could have security tests that should pass before each plugin run, so that in case we push to master and accidently get something messed up and a person also fetches the update at that time - they would immediately see the problem, instead of getting pwn'd.
  - {{[[TODO]]}} #[[(hidden) jOMmlCP4S]] `git-rebase -i` right inside [[github]]'s PR UI lmao

January 14th, 2022 (1)

{{[[TODO]]}} (!) un-pause the [[github actions]] workflow - after stuff like ((LGHGl9_23)) gets done
- [1]
  - ((5oHA_bb-0))

January 16th, 2022 (1)

{{[[TODO]]}} for the [[(hidden) nicjeov_l]] stuff, probably a good time to handle [[(hidden) p6Ml7Gdq_]] - exactly what would help against right now having to pause [[github actions]] workflow.

February 3rd, 2022 (1)

{{[[TODO]]}} thrown error should exit 1 in [[github actions]]

(hidden) hsL43OmNp (1)

(hidden) 3gop-JGHk [[github actions]]

August 2nd, 2022 (3)

[[github actions]]
- [[TIL]]
  - for a `composite` action, you don't need nor should use `actions/checkout` -- your action is already checked out in `${{ github.action_path }}` dir.
    - https://docs.github.com/en/actions/learn-github-actions/contexts#github-context
    - this is why `./something-inside-action-dir.sh` doesn't work -- you need to use `${{ github.action_path }}/something-inside-action-dir.sh`
      - damnit [[github]], this is a very common requirement, and i wasted many hours until i figured this out. why not mention it / make it more obvious?...
  - [[August 29th, 2022]]
    - https://github.com/actions/runner/issues/716#issuecomment-795238933
      - nope
        
        > This property is only supported in composite actions.
        
        asdjkasjhdsakjhdaskjhdasjkdahshjkdashkjdas
[[github actions]]
- here we go again!!! `composite` actions totally broken cannot run the executable; docker action is a pain in the a$$ to setup... [[(hidden) Ux6tvluwa]]
  - okay got it finally after many hours w/ the `docker` action... it's "composable", or rather - gets "inlined" into where the "uses" keyword is used in the original workflow that uses the action.
    - [[github actions]]
      - [[TIL]]
        
        for a `composite` action, you don't need nor should use `actions/checkout` -- your action is already checked out in `${{ github.action_path }}` dir.
        
        https://docs.github.com/en/actions/learn-github-actions/contexts#github-context
        
        this is why `./something-inside-action-dir.sh` doesn't work -- you need to use `${{ github.action_path }}/something-inside-action-dir.sh`
        
        damnit [[github]], this is a very common requirement, and i wasted many hours until i figured this out. why not mention it / make it more obvious?...
        
        [[August 29th, 2022]]
        
        https://github.com/actions/runner/issues/716#issuecomment-795238933
        
        nope
        
        > This property is only supported in composite actions.
        
        asdjkasjhdsakjhdaskjhdasjkdahshjkdashkjdas
- [[userscript]]
  - {{[[TODO]]}} create script to auto-open the job (or choose from jobs) when in the actions view (instead of having to navigate twice)
{{[[DONE]]}} (hidden) 2IW2f-mC6 [[github actions]]
- {{[[TODO]]}} (hidden) syiCYSL6j
- {{[[TODO]]}} (hidden) Gvvs39r-d