File tree 1 file changed +3
-2
lines changed
1 file changed +3
-2
lines changed Original file line number Diff line number Diff line change @@ -63,15 +63,16 @@ pub enum PathFreshness {
63
63
/// The function behaves differently in CI and outside CI.
64
64
///
65
65
/// - Outside CI, we want to find out if `target_paths` were modified in some local commit on
66
- /// top of the local master branch .
66
+ /// top of the latest upstream commit that is available in local git history .
67
67
/// If not, we try to find the most recent upstream commit (which we assume are commits
68
68
/// made by bors) that modified `target_paths`.
69
69
/// We don't want to simply take the latest master commit to avoid changing the output of
70
70
/// this function frequently after rebasing on the latest master branch even if `target_paths`
71
71
/// were not modified upstream in the meantime. In that case we would be redownloading CI
72
72
/// artifacts unnecessarily.
73
73
///
74
- /// - In CI, we always fetch only a single parent merge commit, so we do not have access
74
+ /// - In CI, we use a shallow clone of depth 2, i.e., we fetch only a single parent commit
75
+ /// (which will be the most recent bors merge commit) and do not have access
75
76
/// to the full git history. Luckily, we only need to distinguish between two situations:
76
77
/// 1) The current PR made modifications to `target_paths`.
77
78
/// In that case, a build is typically necessary.
You can’t perform that action at this time.
0 commit comments