▲ 265 ▼ "GitHub CI is easy", he said. "It's just bash ", he said. (programming.dev) submitted 2 years ago* by ulterno@programming.dev to c/programmer_humor@programming.dev 37 comments fedilink hide all child comments Until he actually had to use it. Took 2 hours of reading through examples just to deploy the site. Turns out, it is hard to do even just the bash stuff when you can't see the container.
[+] smeg@feddit.uk 23 points 2 years ago (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@programming.dev [S] 1 point 2 years ago (1 child) Well, it does have triggers for other branches: on: push: branches: [ "main" ] pull_request: branches: [ "main" ] So, most probably would have a way to run it on other branches. permalink fedilink source parent hideshow 2 child comments replies: [–] odelik@lemmy.today 7 points 2 years ago (1 child) You can also use the workflow_dispatch execution pattern and use some data input params and execute through the portal interface. However, do be careful about trusting input params without sanitizing them (GH has docs around this). permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@programming.dev [S] 1 point 2 years ago Thanks, I'll look into that. While trying this time (as you can see in one of the commits), I added workflow_dispatch at the wrong place, causing a problem. Later realised that it is part of the on permalink fedilink source parent
[–] ulterno@programming.dev [S] 1 point 2 years ago (1 child) Well, it does have triggers for other branches: on: push: branches: [ "main" ] pull_request: branches: [ "main" ] So, most probably would have a way to run it on other branches. permalink fedilink source parent hideshow 2 child comments replies: [–] odelik@lemmy.today 7 points 2 years ago (1 child) You can also use the workflow_dispatch execution pattern and use some data input params and execute through the portal interface. However, do be careful about trusting input params without sanitizing them (GH has docs around this). permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@programming.dev [S] 1 point 2 years ago Thanks, I'll look into that. While trying this time (as you can see in one of the commits), I added workflow_dispatch at the wrong place, causing a problem. Later realised that it is part of the on permalink fedilink source parent
[–] odelik@lemmy.today 7 points 2 years ago (1 child) You can also use the workflow_dispatch execution pattern and use some data input params and execute through the portal interface. However, do be careful about trusting input params without sanitizing them (GH has docs around this). permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@programming.dev [S] 1 point 2 years ago Thanks, I'll look into that. While trying this time (as you can see in one of the commits), I added workflow_dispatch at the wrong place, causing a problem. Later realised that it is part of the on permalink fedilink source parent
[–] ulterno@programming.dev [S] 1 point 2 years ago Thanks, I'll look into that. While trying this time (as you can see in one of the commits), I added workflow_dispatch at the wrong place, causing a problem. Later realised that it is part of the on permalink fedilink source parent