devabhishekpal commented on PR #6916: URL: https://github.com/apache/ozone/pull/6916#issuecomment-2254354827
Hi @sarvekshayr, thanks for adding this patch and @errose28 for your inputs. I believe it would be better to use GitHub actions for committing the result rather than using a plugin. What we could do is: - After the build step we can upload the generated files as artifacts (there is a GitHub action `actions/upload-artifact@v4` which stores the artifacts generated during a workflow for consumption later) - We add a workflow to download these uploaded artifacts (`actions/download-artifact@v4`) and as you suggested use shell commands to detect the generated xml files and transform them. - This can then be committed back into the same PR like we did for the dependabot script or raise a separate PR for both ozone-site (for the new website) and hdds-docs. @sarvekshayr please refer below on how you might be able to share the data between the workflows: https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts And for pushing the commit you can check the changes that were done for dependabot if you want to add the generated markdown file to the same PR. [This](https://github.com/devabhishekpal/ozone/blob/dd97b156abdbae8d64d38e440c6671cdfca7c40b/.github/workflows/dependabot-ci.yml#L68) is the reference to the line where that step is being executed. Or you can use the bot to raise a separate PR for better tracking via GitHub actions. -- 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]
