-
Notifications
You must be signed in to change notification settings - Fork 287
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
added autobuild and autorelease workflow for the newest build #191
base: main
Are you sure you want to change the base?
Conversation
if: ${{ steps.latest_release.outputs.release != steps.previous_release.outputs.release }} | ||
|
||
- name: Create release | ||
uses: actions/create-release@v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I use https://github.com/softprops/action-gh-release for creating GH releases in my own projects. Works pretty well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would be great!
The action looks good.
@aleksanderbl29 How come then that this is not yet merged? |
@watchingdogs On the other hand you could question if it is really needed to have the absolute newest updates at all times - I like it, but def isn't needed. |
… change cron-schedule
Add auto-build-container.yml according to upstream chriscrowe#191 and change cr…
Took the pr 147 from @tritethunder as an idea and reworked it a little bit. Sorry if i could have done that in his pr i am pretty new to git and github.
The workflow now checks if there is a new pihole container release, builds it and creates a new release in this repo.
Only caveat is that actions/create-release is not maintained anymore and uses NodeJS 12 and set-output. So maybe creating it automatically is not the best path.
You still have to put your dockerhub username and token under settings->secrets->actions