[Backport 1.x] Auto-increment next development iteration.#2164
Conversation
|
Can one of the admins verify this patch? |
|
@VachaShah care to help with this? thanks |
@dblock I opened a manual backport PR #2306 but the DCO fails for that too. Is there something that changed for your DCO? Also, I think you would be able to amend the commit in this auto backport PR to fix the DCO. When the backport workflow runs, it picks the author as the name and email of the user which can be different from the DCO sign (reference #2165). So the DCO failure in this PR makes sense. Also, we have the new DCO app now running on PRs which helps fix this issue. But I am not sure why the DCO is failing in a manual backport. |
d2a4336 to
9d4a316
Compare
* Auto-increment next development iteration. Signed-off-by: dblock <dblock@amazon.com> * Make bwc increments on X.Y and main branches. Signed-off-by: dblock <dblock@amazon.com> Signed-off-by: dblock <dblock@dblock.org>
9d4a316 to
de8bba2
Compare
|
Looks like it has something to do with me working on two different machines where one is set to my amazon email and the other to personal. I rebased/signed/amended this PR. |
|
❌ Gradle Check failure d2a43369b959ec3914edca3b582aa7d58c215487 |
Backport 7a38109 from #1816