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
We are no longer "mounting" enlistments, so we do not regularly update the Git config for a Scalar enlistment. As we create new versions, we will want to update the config as necessary. We should also be very careful about the "compat" scenario when someone upgrades and uses their repo before the maintenance step is run. However, it would be good to run the config as soon as possible after the service starts up (and then at some cadence, such as daily?).
The text was updated successfully, but these errors were encountered:
These commits are cherry-picked from #258 with slight modifications. The functionality here makes sense for repos cloned by Scalar, allowing us to focus later on the interactions with vanilla Git repos.
1. Add `ConfigStep` for running the Git config commands at clone time and as the service starts up. This already has some split for vanilla Git repos, but that code does not get exercised. Resolves#252.
2. The `PackfileMaintenanceStep` attempts to repack all but the largest pack when those packs sum to less than 2gb.
3. Some cleanup things here and there.
4. `scalar repos (add|list)` allows tracking the registered repos. Resolves some of #214.
We are no longer "mounting" enlistments, so we do not regularly update the Git config for a Scalar enlistment. As we create new versions, we will want to update the config as necessary. We should also be very careful about the "compat" scenario when someone upgrades and uses their repo before the maintenance step is run. However, it would be good to run the config as soon as possible after the service starts up (and then at some cadence, such as daily?).
The text was updated successfully, but these errors were encountered: