[Proposal] Track Submodule pymc-examples Git Fix

[CloudChaoszero]

Overview

Proposed 🤞 fix to track submodule pymc-examples to the main branch.

• Configure .gitmodules to specify branch for submodule

(potentially) closes #4357

However, there are some notes... ⬇️

Notes

• I was not able to locally update (from the command below) due to permission issues.
  git submodule update --remote

You can see this error to align commit to main branch here

[codecov]

Codecov Report

Merging #4375 (1439ba7) into master (0402aab) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4375   +/-   ##
=======================================
  Coverage   87.95%   87.96%           
=======================================
  Files          88       88           
  Lines       14493    14501    +8     
=======================================
+ Hits        12748    12756    +8     
  Misses       1745     1745           

Impacted Files	Coverage Δ
pymc3/model.py	89.29% <0.00%> (+0.01%)	⬆️
pymc3/distributions/dist_math.py	92.17% <0.00%> (+0.20%)	⬆️

[MarcoGorelli]

I presume this doesn't work for you because you don't have ssh keys set up. Perhaps we can change this line to

Suggested change

	url = git@github.com:pymc-devs/pymc-examples.git
	url = https://github.com/pymc-devs/pymc-examples.git

[CloudChaoszero]

Ah, I see @MarcoGorelli. Thanks!

Did that. Following, I did a git submodule sync, based on this article.

---

Process now looked like:
0. Edit the .gitmodules file

1. git submodule sync
2. git submodule update --remote
3. git checkout main (on the submodule)
4. Went to parent module, and committed changes

[CloudChaoszero]

Update made, well I hope.

Before going into recommended updates from the original suggested article, here, I did the following:

---

Process now looked like:

1. Edit the .gitmodules file
2. git submodule sync, based on this article.
3. git submodule update --remote
4. git checkout main (on the submodule)
5. Went to parent module, and committed changes

---

Oddly, the submodule is pointed to a commit SHA, and not main. (I think that's expected?)

That being said, going forward, updating that submodule maaaaaay look like git submodule update --remote command only.

[MarcoGorelli]

Thanks, this looks right

Can you just update build_and_deploy_docs.sh as well?

[CloudChaoszero]

Thanks, this looks right

Can you just update build_and_deploy_docs.sh as well?

Sounds great! Changed the git submodule line, line 6, to the one that i used.

[MarcoGorelli]

Thanks @CloudChaoszero

cc @ColCarroll