Github on kenji.blog

Looking for GitHub Sponsors

Tue, 17 Jan 2023 18:13:56 +0900

Looking for GitHub Sponsors

I would be happy if you could become a GitHub sponsor via the button below.

The funds will be used for tool development and related activities.

I will do my best until I can afford to attach a code signing certificate!

Dynamically setting variables in Github Actions

Sun, 02 Oct 2022 02:33:35 +0900

To dynamically set variables in Github Actions, you can achieve this by appending to $GITHUB_ENV as shown below.

[For Windows]

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44


name: Rust

on:
 push:
 branches: [ "master" ]
 pull_request:
 branches: [ "master" ]

env:
 CARGO_TERM_COLOR: always

jobs:
 build:
 runs-on: ubuntu-latest
 steps:
 - uses: actions/checkout@v3
 - name: Get Environment
 run: |
 echo 'VERSION=1.0.0' >> $GITHUB_ENV
 echo 'NAME=1.0.0' >> $GITHUB_ENV
 - name: Display Environment
 run: |
 echo $env:VERSION
 echo $env:NAME
 - name: Create Release
 id: create_release
 uses: actions/create-release@v1
 env:
 GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 with:
 tag_name: ${{ env.VERSION }}
 release_name: ${{ env.VERSION }}
 draft: false
 prerelease: false
 - name: Upload Release Asset
 id: upload-release-asset
 uses: actions/upload-release-asset@v1
 env:
 GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 with:
 upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
 asset_path: ./target/release/${{ env.NAME }}.exe
 asset_name: ${{ env.NAME }}.exe
 asset_content_type: application/octet-stream

[For Linux]

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24


name: Rust

on:
 push:
 branches: [ "main" ]
 pull_request:
 branches: [ "main" ]

env:
 CARGO_TERM_COLOR: always

jobs:
 build:
 runs-on: ubuntu-latest
 steps:
 - uses: actions/checkout@v3
 - name: Get Environment
 run: |
 echo 'VERSION=1.0.0' >> $GITHUB_ENV
 echo 'NAME=hello' >> $GITHUB_ENV
 - name: Display Environment
 run: |
 echo ${{ env.VERSION }}
 echo ${{ env.NAME }}

How to set up a custom domain for a Github repository

Tue, 13 Sep 2022 01:16:40 +0900

To set up a custom domain for a Github repository, you need to change the domain’s DNS settings. Here, we will explain assuming that you manage your domain with Onamae.com . Similar settings can be applied by rewriting the A record with other registrars as well.

Change DNS settings on Onamae.com

To change the DNS settings of your domain, log in to the management screen of Onamae.com . After logging in, go to the domain management screen. Once on the domain management screen, change the DNS settings. To change the DNS settings, configure them as follows:

Access https://www.onamae.com/ and click “Onamae.com Navi Login”
Enter your “Onamae ID (Member ID)” and “Password” and click the login button
Click “Name Server Settings”
Click “Domain DNS Settings”
Select the domain you want to set up and click “Next”
Click “Set up” to the right of “Use DNS record settings”
Select A for TYPE, enter 3600 for TTL, enter “185.199.108.153” for VALUE, and click “Add”
Add “185.199.109.153”, “185.199.110.153”, and “185.199.111.153” in the same way as step 7.
Ensure that the checkbox in “Confirm name server change for DNS record settings” is checked and click “Proceed to setting screen”
If the screen “To prevent unintended DNS setting changes” appears, click “Do not set” (select as necessary)
Confirm the setting details and click “Set up”
This completes the DNS settings. It may take up to 72 hours for the reflection to complete.
If it is not reflected after 72 hours, please try contacting Onamae.com support.

To check if the settings have been reflected in your local environment, try executing the following commands. Please replace the example.com part with the domain you want to check.

For Linux and Mac

1

dig example.com +noall +answer -t A

If the result looks like the following, the settings have been reflected.

1
2
3
4


example.com. 0 IN A 185.199.108.153
example.com. 0 IN A 185.199.109.153
example.com. 0 IN A 185.199.110.153
example.com. 0 IN A 185.199.111.153

For Windows

1

nslookup -q=a example.com 8.8.8.8

If the result looks like the following, the settings have been reflected.

1
2
3
4
5
6
7
8
9


Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: example.com
Addresses: 185.199.108.153
 185.199.109.153
 185.199.110.153
 185.199.111.153

Set a custom domain in the Github repository

Open the repository page and click Settings
Click Pages
If you want to publish the repository source as is, select “Deploy from a branch” in Source. If you want to build the source using HUGO or similar, select “GitHub Actions”.
Select the branch to publish in Branch and click Save
Enter the acquired domain in Custom domain and click Save.
Check “Enforce HTTPS” as necessary to support HTTPS

[PR]