Make submodules track master branches #227
Conversation
|
I'm not going to move the HEAD of |
lzaoral
force-pushed
the
submodule-always-track-master
branch
from
a54f658 to
d9a3c0e
Compare
|
@trtikm We can use GitHub's Dependabot to automatically create PRs with submodule updates, run the build and test-suite and merge them if it succeeds. That should be much safer and less breakage-prone than to always pull HEAD of the submodule in the build script and not necessarily testing the new version in CI. |
The same setting was already applied for dg and sbt-{intrumentation,slicer}.
lzaoral
force-pushed
the
submodule-always-track-master
branch
from
d9a3c0e to
f09a8e0
Compare
lzaoral
changed the title
There was a problem hiding this comment.
Git started recently using main as the "master" branch. If we want to follow this convention, I think this is the right point where to start. That is, finish merging SV-COMP 22 changes to modules, create new main branches and then merge this PR changed to track main branches. If you want to continue with master branches, I'll approve the commit.
| [submodule "klee"] | ||
| path = klee | ||
| url = https://github.com/staticafi/klee | ||
| ignore = untracked | ||
| branch = 9.0.0-dev |
There was a problem hiding this comment.
KLEE won't have the master branch stable?
There was a problem hiding this comment.
At the moment, KLEE does not contain any branch that's called master or main and 9.0.0-dev seems to be the latest development branch at the moment.
That's a really good idea, @mchalupa! I'll mark this PR as a draft for now. |
As agreed on Monday's (9. 5.) meeting, from now on the submodules should track changes in corresponding
masterbranches only. Only these branches are now considered to be stable.If you want to update the modules to the HEAD, just run
git submodule update --remoteand commit the changes to this repo.