Conversation
83f1a04 to
0562ec6
Compare
0562ec6 to
b97380f
Compare
b97380f to
e923356
Compare
e923356 to
c7d3513
Compare
|
I've changed the event in |
|
@Betree Could you please take a look? |
|
This is a really good idea and quite necessary for this lib (I think). @dolfinus I see on your branch that the github actions have not run for a few months. https://github.com/wesbos/burner-email-providers was updated 25 days ago with a new list. I thought the github actions would update with this new list? Am I missing something? Do the actions only run every day on |
|
Hi.
I've disabled this action just to stop it from adding new commits and making this PR full of unrelated changes. I could create another branch with the same change to demonstrate the workflow if you wish. |
No need to create another branch. I understand. I hope this gets approved and merged. |
72313be to
fb9e5a9
Compare
|
I've added a Example run of the Example run of the triggered by commit This run generated a new tag 3.1.1: |
22cc550 to
1921973
Compare
1921973 to
982a0ed
Compare
|
@Betree Can this be merged please? It would be a great addition. |
Hello.
I found a beautiful solution of automatic updates of emails.txt file using Github Actions.
Here is the source: https://github.com/lindell/go-burner-email-providers/blob/main/.github/workflows/build.yaml
How it works:
There are 2 things that should be done:
repo. It will be used to push new commit with updated emails list, and also pushing new tags. DefaultGITHUB_TOKENis not suitable here because it does not trigger workflows which is important for making automatic releases.mix hex.user key generate --permission api:write. It will be used to publish new package releases.