Closed FlorianDeconinck closed 10 months ago
Look north son, you hear this howling that the winds carries? This comes from the land of Vermont, where souls are being tortured
We ran into this with a branch in another repo where it thinks the branch is ahead of main, even though it isn't (like your 0 files different indicates). Turns out it sees every pull from main as a new commit and that cascades down if each of the commits you bring in has a pull from main...
Is there something we can do to keep that from happening in the future?
Well what I'll do going forward is to go NOAA/main
---(with website sync)---> NASA/main
-----> NASA/geos/main
hopefully using their own website interface will help.
Github has been adamant that the NASA forks is 66 commits ahead. It is not - as the 0 files changed here demonstrated.
This PR is an attempt to make Github stop complaining.