Open PRs to bump the e-Paper submodule automatically - #3
Open
TomerAberbach wants to merge 1 commit into
Open
Conversation
Dependabot's gitsubmodule ecosystem opens the PR when upstream moves, which avoids a scheduled workflow polling the API and a PAT to push branches. The smoke test gives those PRs something to verify. epaper/__init__.py hardcodes the driver path under RaspberryPi_JetsonNano, so a bump that moves it leaves modules() empty. Importing a driver needs RPi.GPIO and a real Pi, so the check stops at the import of epaper itself and needs no poetry install. publish.yml switches to the checkout submodules option so both workflows fetch the submodule the same way.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Just thought I'd make your life easier (and make me happy knowing the package I'm depending on stays updated!)
Dependabot's gitsubmodule ecosystem opens the PR when upstream moves, which avoids a scheduled workflow polling the API and a PAT to push branches.
The smoke test gives those PRs something to verify. epaper/init.py hardcodes the driver path under RaspberryPi_JetsonNano, so a bump that moves it leaves modules() empty. Importing a driver needs RPi.GPIO and a real Pi, so the check stops at the import of epaper itself and needs no poetry install.
publish.yml switches to the checkout submodules option so both workflows fetch the submodule the same way.