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
When we switch back and forth between the old and recent branches,
if there was a breaking change in the bootstrap configuration in
between, we have to update the change-id in the build configuration
with each checkout, which can be exhausting. This change fixes that.
Signed-off-by: onur-ozkan <work@onurozkan.dev>
msg.push_str("WARNING: there have been changes to x.py since you last updated.\n");
120
120
msg.push_str("To see more detail about these changes, visit the following PRs:\n");
121
+
121
122
for link in change_links {
122
123
msg.push_str(&format!(" - {link}\n"));
123
124
}
125
+
126
+
msg.push_str("WARNING: there have been changes to x.py since you last updated.\n");
127
+
128
+
msg.push_str("note: to silence this warning, ");
129
+
msg.push_str(&format!(
130
+
"update `config.toml` to use `change-id = {latest_config_id}` instead"
131
+
));
124
132
}
125
-
msg.push_str("WARNING: there have been changes to x.py since you last updated.\n");
126
-
format!("update `config.toml` to use `change-id = {latest_config_id}` instead")
127
133
}else{
128
134
returnNone;
129
135
}
130
136
}else{
131
137
msg.push_str("WARNING: The `change-id` is missing in the `config.toml`. This means that you will not be able to track the major changes made to the bootstrap configurations.\n");
132
-
format!("add `change-id = {latest_config_id}` at the top of `config.toml`")
138
+
msg.push_str("note: to silence this warning, ");
139
+
msg.push_str(&format!("add `change-id = {latest_config_id}` at the top of `config.toml`"));
0 commit comments