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

cFS submodules refer to "master" branches #376

Closed
CDKnightNASA opened this issue Oct 14, 2021 · 1 comment · Fixed by #377 or #371
Closed

cFS submodules refer to "master" branches #376

CDKnightNASA opened this issue Oct 14, 2021 · 1 comment · Fixed by #377 or #371
Assignees

Comments

@CDKnightNASA
Copy link
Contributor

It seems the .gitmodules file still lists "branch = master" for cfe and osal. Should switch to "main". (Surprised "master" still works, given that branch is long gone! Guessing git defaults to "HEAD" if the branch specified no longer exists.)

branch = master

@skliper
Copy link
Contributor

skliper commented Oct 15, 2021

From what I can tell the branch setting in .gitmodules only really matters if you do a git submodule update --remote which isn't really a normal user thing in our flow since the refs you get from the cFS repo gets you something that has gone through the cFS CI. It's a good fix, but shouldn't actually matter unless you are using that command. Not being all that familiar w/ the command above, I typically just use git submodule foreach git checkout main and a corresponding pull.

astrogeco added a commit that referenced this issue Oct 18, 2021
fix #376, "main" branch for cfe and osal submodules
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants