Before following this tutorial, please make sure to have an active Github account.
There are four main steps to configure the bot to access your local repository and logbook account;
- Fork the project to your Github account
- Make a Github token to access the repository. This is used to make a local daily log of your logbook.
- Make repository secrets. These values are used to access your repository and logbook page.
- Add Github Actions
- Fork the project repository to your Github account
-
Click your profile and select "Settings"
-
On the bottom left of the page, click "Developer settings"
-
On the left, you will find a sidebar. Click on "Personal access token"
-
Fill in the note and check the required permissions for the bot to access the repository
-
You will get your Github token. COPY IT IMMEDIATELY, once you refresh/reload the page, you will not see the code again
-
Go back to your forked repository settings. On the left, you will find a sidebar. Click on "Secrets"
-
Here, you will need to create new secrets.
These values are used to access the repository and your logbook page
| Name | Value |
|---|---|
MY_GITHUB_TOKEN |
Paste your github token you previously made |
MY_USERNAME |
Your BINUS ID (NIM) |
MY_PASSWORD |
Your account password |
Secrets are encrypted and is only accessable by the repository in your own account, so it won't be visible to anyone.
-
Open this link on new tab, then copy the whole script
-
Go to the Actions tab, and set a new workflow
-
Choose "set up workflow yourself"
-
Delete the boilerplate and paste the whole script there, and name it
autofill.yml
-
On line 40, there will be a step to commit data to your forked repository. Replace
INSERT_YOUR_GITHUB_EMAIL_HEREandINSERT_YOUR_GITHUB_USERNAME_HEREwith your credentials.
That's it! Github Actions will use that value to access the repository and your logbook account to automatically fill your logbook.
