The First Time I Saw an Automated Task Change, I Panicked
Late one night last week, I opened my GitHub project and found an extra step in the automatic publishing flow: it downloaded an unfamiliar script. It used to only tidy up text; now it could access customer files in the repository. I stopped the workflow immediately, but my palms were still sweating. Only later did I realize that these “helpful little robots” save time while also handing part of the decision-making power to third parties.
I’m not saying everyone using GitHub Actions should lock down every task today. First, I’d identify the tasks that, if altered, could touch customer files, send messages, or spend money.
What It Is, and Why People Use It
Simply put, GitHub Actions lets GitHub do things step by step: test after every code commit, generate files, publish content. Adding manual approval to a critical step is like putting a lock on the office door that only you can open. The workflow reaches the door, waits for me to click “Approve,” and only then continues.
I know an indie developer, Lin Zhe, who takes remote contract projects in Hangzhou. He requires manual approval for “update the client delivery package” so an automated workflow cannot accidentally overwrite files. Another freelancer, A Chen, maintains a personal website in Shenzhen. He locks only the step that publishes live content; test tasks still run automatically. That way, there’s less hassle without throwing away every convenience.
What It Costs to Replicate Today
Money: GitHub’s free personal tier is usually enough for a small project, and the extra configuration generally costs 0 yuan; if you use a team plan, your actual bill is the deciding factor.
Time: The first pass takes about 30–60 minutes; adding the lock itself usually takes around 10 minutes.
Technical barrier: I need to read a little GitHub workflow configuration, but no advanced programming skills. On the first try, I can follow the documentation line by line.
First step: Open the GitHub repository, click “Actions,” enter the workflow I use most, then click “Edit workflow file” in the upper-right corner. Find the step that needs confirmation and add the manual approval setting. I won’t start with an important repository; I’ll practice on a test project first.
Depending on My Current Stage, Here’s What I’d Lock
If I’m just starting and the project has no formal clients yet, I’d keep the default settings and only disable third-party connections I don’t need. Not every tool suits every setup, and there’s no rush to try this now.
If I already have one or two clients, I’d review every step involving client files, email, and payments, then add manual approval to the one or two most critical steps.
If I’m scaling up, I’d do more than lock the workflow: I’d also review automated tasks and access permissions once a month, and separate the approver from the backup owner. I’m not doing this to look overly cautious. I’m doing it so that, when something breaks, another person can take over quickly.