Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: automate using GitHub Actions #36

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

dnhn
Copy link
Contributor

@dnhn dnhn commented Aug 18, 2023

I have written a workflow for automating content generation upon the merging of pull requests. It simply involves making edits to the data.json, eliminating the need for manual content generation.

Here is a successful execution of this workflow on my fork:
https://github.com/dnhn/fe-pedia-paradite-actions/actions/runs/5903648824

To ensure the successful pushing of commits through this workflow, it is required that read and write permissions are granted to the workflow in repository Settings > Actions.

Trigger a workflow on a pull request merge to generate contents automatically.
@paradite
Copy link
Owner

I didn't add the action because I don't want to have another entry in the list of files on home page.
One more entry means people have to scroll down more to see the README.md.

I will keep this PR open until I decide on how to make it a website, which can be done together with PR.

@paradite
Copy link
Owner

see #25

@paradite
Copy link
Owner

Also I am not sure where you got the user name and email for the GitHub action bot.

I use the following for my repos:

          git config --global user.email "github@action"
          git config --global user.name "GitHub Action"

@dnhn
Copy link
Contributor Author

dnhn commented Aug 19, 2023

I didn't add the action because I don't want to have another entry in the list of files on home page. One more entry means people have to scroll down more to see the README.md.

I will keep this PR open until I decide on how to make it a website, which can be done together with PR.

I understand your point and saw your plan for the website too, I thought that the action could be achieved simply for now. If the website is implemented, this action might not be necessary anymore.


Also I am not sure where you got the user name and email for the GitHub action bot.

I use the following for my repos:

This is taken from the bot’s commits across various repositories. I have just found another source below and have updated it with a more appropriate email, tested and it worked:
https://github.com/actions/deploy-pages/blob/main/.github/workflows/rebuild-dependabot-prs.yml#L47C78-L47C78

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants