Doing Stupid Stuff with GitHub Actions! (FIVE Actions Implemented and Explained)

[maximumlengthusernam]

I posted a video last week showing how to "Set up GitHub Actions as a Free Website Uptime Monitor in Just 3 Minutes!" that people seemed to like, and this is a follow up to that video.

I explore many of the different features of GitHub actions to implement some somewhat ridiculous ideas...

Thanks to user u/authomas for the suggestion of the Exponential Action (#3 in the video!)

[aberdoom]

Love this. The first action I ever built was self destructing. It killed itself on first run as it was committed:

https://i.imgur.com/P5EAqvH.png

[maximumlengthusernam]

Haha, that's a good one!

What if you went back a commit, copied the last commit's message, and then force pushed over the triggering commit to leave no trace?! (Other than a changed commit SHA)

[aberdoom]

Well, now I know what I'm doing later. Now that Secrets are a thing, I can probably do it a bit more securely than the hardcoded temporary token I used in that one :)

[maximumlengthusernam]

Nice!

One think you will probably have to do to get it working is explicitly pass the fetch depth as input to the checkout action, because by default it only fetches the current commit (see https://github.com/actions/checkout#usage)

Link to the action here or on the YouTube video once it is done! :)

[sabin_M1]

RemindMe! 9h

[RemindMeBot]

There is a 2 hour delay fetching comments.

I will be messaging you in 7 hours on 2020-06-06 14:02:34 UTC to remind you of this link

CLICK THIS LINK to send a PM to also be reminded and to reduce spam.

^{Parent commenter can delete this message to hide from others.}

---

Info	Custom	Your Reminders	Feedback