sravani-revuri opened a new pull request, #10826:
URL: https://github.com/apache/ozone/pull/10826
## What changes were proposed in this pull request?
The update-ozone-site-config-doc workflow in the ozone repo checks out the
automated-config-doc-update branch in ozone-site when it still exists after a
PR is merged. New commits are added on top of that stale branch, so
already-merged changes show up again in the next PR.
Workaround: Delete automated-config-doc-update in ozone-site after each
merge.
Fix: Always use master as the baseline - compare doc changes against master,
recreate the PR branch from master. Branch deletion after merge should no
longer be required.
Example:
https://github.com/apache/ozone-site/pull/487 merged commits
[68268fa](https://github.com/apache/ozone-site/pull/487/commits/68268fa817be5d3550f22c8dfcc70c7dbcb5d612)
and
[a8e25a6](https://github.com/apache/ozone-site/pull/487/commits/a8e25a6ab70447c7399210f2aa3b6b2bf3fff464)
but branch not deleted.
https://github.com/apache/ozone-site/pull/493 same commits have reappeared
here.
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-15922
## How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests,
workflow run on the fork git repo.)
(If this patch involves UI changes, please attach a screenshot; otherwise,
remove this.)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
