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
Warn if workflow for automated version increments cannot modify PR
It it's a constant source of confusion that the commit with version
increments is not pushed to the PR, in case edits by maintainers are
disabled or the PR is created from an organization repository (which
makes edits in general impossible).
This now adds a warning for that case to at least explain contributors
the situation.
? "An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the _git patch_."
123
+
: ":warning: :construction: **This PR cannot be modified by maintainers** because edits are disabled or it is created from an organization repository. To obtain the required changes apply the _git patch_ manually as additional commit."
116
124
const commentBody = `
117
125
${{ env.COMMENT_FIRST_LINE }}.
118
126
Therefore the following files need a version increment:
119
127
\`\`\`
120
128
${fileList}
121
129
\`\`\`
122
-
An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the _git patch_.
130
+
${applyChangeMessagePart}
123
131
<details>
124
132
<summary>Git patch</summary>
125
133
@@ -130,7 +138,6 @@ jobs:
130
138
131
139
Further information are available in [Common Build Issues - Missing version increments](https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/wiki/Common-Build-Issues#missing-version-increments).
0 commit comments