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

Minor refactoring #90

Merged
merged 4 commits into from
Jan 24, 2023
Merged

Minor refactoring #90

merged 4 commits into from
Jan 24, 2023

Conversation

sebthom
Copy link
Contributor

@sebthom sebthom commented Jan 3, 2023

This PR addresses some low hanging fruits and adds a github action that automatically runs shellcheck.

@djmaze
Copy link
Collaborator

djmaze commented Jan 18, 2023

Thanks, but I don't know why we need github actions. I am striving to decentralize and my drone instance is already running the tests.

Copy link
Collaborator

@djmaze djmaze left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really a small refactoring ;)

Apart from the github action (which I do not want), looks good to me.

@sebthom
Copy link
Contributor Author

sebthom commented Jan 18, 2023

The reason why I added the github action is, that it will also run in forks without requiring to create a PR first to get feedback from your drone instance.

shepherd Outdated Show resolved Hide resolved
@sebthom
Copy link
Contributor Author

sebthom commented Jan 19, 2023

I have removed the Github action configuration, but I would ask you to reconsider adding it in light of the external contributions.
GHA actions are free for public repos, and since you can still run your drone instance, this does not get in the way of your desire to decentralise.

@sebthom sebthom requested a review from djmaze January 20, 2023 21:38
@djmaze
Copy link
Collaborator

djmaze commented Jan 21, 2023

Okay, that makes sense, and I don't have a good alternative on my mind currently. I also see in your fork that the action is working correctly. So I would be okay with re-adding the action.

@sebthom
Copy link
Contributor Author

sebthom commented Jan 24, 2023

Okay, that makes sense, and I don't have a good alternative on my mind currently. I also see in your fork that the action is working correctly. So I would be okay with re-adding the action.

I added the gha job again. sorry for the delay

@djmaze
Copy link
Collaborator

djmaze commented Jan 24, 2023

Okay cool, thanks!

@djmaze djmaze merged commit e1a6e34 into containrrr:master Jan 24, 2023
@djmaze djmaze added this to the 0.7.1 milestone Jan 24, 2023
@sebthom sebthom deleted the patch-01 branch January 24, 2023 23:02
moschlar added a commit that referenced this pull request Oct 30, 2023
[Full Changelog](0.7.0...1.8.0)

**Breaking changes:**

- The docker image registry location has been changed to the containrrr organisation:
  `containrrr/shepherd`

**Implemented enhancements:**

- armhf support [\#108](#108)
- Switch to official docker image v24 [\#107](#107) ([djmaze](https://github.com/djmaze))
- Restrict runtime of "docker service update" using "timeout" [\#98](#98) ([fooflington](https://github.com/fooflington))
- Add example for usage with swarm-cronjob [\#89](#89) ([djmaze](https://github.com/djmaze))

**Fixed bugs:**

- Can't update some services: no such manifest [\#105](#105)
- Service gets stuck when calling "docker service update" and won't progress [\#97](#97)
- fix: docker service update with `--detach=false` hangs on services wi… [\#104](#104) ([AliRezaBeitari](https://github.com/AliRezaBeitari))
- Fix defunc VERBOSE handling [\#91](#91) ([sebthom](https://github.com/sebthom))

**Closed issues:**

- How does it determine if there is an update or not? [\#111](#111)
- Looking for a new maintainer [\#96](#96)
- New OCI manifest issue [\#92](#92)
- Run service update at a fixed time [\#88](#88)
- docker swarm 20.10.12 | "docker service update" requires exactly 1 argument. [\#83](#83)
- Error updating service, does not exist or it is not available when using a duplicate registry [\#78](#78)

**Merged pull requests:**

- Add apprise type and additional error notification [\#118](#118) ([andyloree](https://github.com/andyloree))
- Rename image in docs [\#114](#114) ([moschlar](https://github.com/moschlar))
- Fix release workflow [\#113](#113) ([moschlar](https://github.com/moschlar))
- Update README.md [\#103](#103) ([andrew-dixon](https://github.com/andrew-dixon))
- ci: add basic github actions for build/release [\#101](#101) ([piksel](https://github.com/piksel))
- correct misleading description of WITH\_NO\_RESOLVE\_IMAGE [\#100](#100) ([alex-vg](https://github.com/alex-vg))
- Move example configs to their own folder [\#99](#99) ([djmaze](https://github.com/djmaze))
- Add documentation about `REGISTRIES_FILE` [\#94](#94) ([tito](https://github.com/tito))
- Minor refactoring [\#90](#90) ([sebthom](https://github.com/sebthom))

Closes: #117
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