You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To do this in general, such a github action would need to be configured with the path within a repo where the subtree lives, likely need to support both git-subtree as well as git-submodule (and possibly git-subrepo), and allow for passing options to the subtree/submodule command (e.g. if someone wanted a git subtree pull --squash to be the PR).
It's unclear that this should live in this precise repo rather than an adjacent one, but putting it here to track/ack the request.
The text was updated successfully, but these errors were encountered:
Julian
added
the
enhancement
An enhancement to the tooling or structure of the suite (as opposed to a new test).
label
Apr 11, 2022
or so. No subtrees though (dependabot/dependabot-core#3741), and I hadn't even heard of git-subrepo, looks like it is a third-party addon.
Julian
changed the title
Provide a GitHub Action for Auto-updating a subrepo of the test suite within implementations
Document how to use Dependabot to keep a test suite submodule up to date
Dec 29, 2022
That sounds perfect I think, and I'd forgotten about it -- changing the title to instead just say we should document exactly what you wrote pretty much.
(Via @Relequestual here)
Implementers may appreciate a GitHub action which automatically sends PRs to their repo to update the test suite.
As a concrete example,
python-jsonschema
has agit-subtree
of this suite here, and would benefit from automated pull requests whenever themain
branch of this repository is updated.To do this in general, such a github action would need to be configured with the path within a repo where the subtree lives, likely need to support both
git-subtree
as well asgit-submodule
(and possiblygit-subrepo
), and allow for passing options to the subtree/submodule command (e.g. if someone wanted agit subtree pull --squash
to be the PR).It's unclear that this should live in this precise repo rather than an adjacent one, but putting it here to track/ack the request.
The text was updated successfully, but these errors were encountered: