Github Actions
(Github Actions) Executing with Github Runner when Self-Hosted Runner Fails
Recently, at our company, we transitioned from the Jenkins CI/CD we used to use to Github Actions, and began using the Self-Hosted Runner. Self-Hosted Runner? As the name suggests, a Self-Hosted Runner means a runner that is self-hosted. Instead of using a runner provided by Github when executing Github Actions, you use a machine that you have hosted yourself. Since you are using your own computer directly, there can often be problems due to environmental constraints or cache issues, but it is faster and (excluding electricity costs) free to use compared to the Github Runner.
October 21, 2024
Automatically Set Labels Based on Github PR (Pull Request) Titles and Issue Titles
While reviewing our company’s project, I found an action that is being used effectively, so I decided to post about it. It is an action that automatically sets labels based on the PR title. Typically, labels are attached to Github issues or PRs to easily categorize them. This is to facilitate history tracking or filtering of what types of issues or PRs existed later on. (It also makes the issues or PRs look prettier.)
May 27, 2024
How to Automatically Assign Assignees and Reviewers in PR (Pull Request)
When developing in a company, there are times when trivial things become annoying. For example, there might be rules requiring specific labels or designating specific Assignees and Reviewers when raising a PR, which are simple but tedious and easy to forget… Such things seem to be the case. It was the same when I first joined the company; determining which label to attach and which Reviewer to designate seemed cumbersome.
May 23, 2024