We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very minor suggestion for the update_post workflow:
Allow for an (optional) preceding '_posts/' in the value for the update_post workflow post_name param.
Why?
If you go to the 'files' view for PR that might need an update, e.g.
https://github.com/wildfly/wildfly.org/pull/562/files
In the heading for single file in the PR the Github UI has a icon that lets you copy the file name, e.g.
_posts/2024-03-05-wildfly-gitops.md
Click that and the pasting the value into the update_post workflow dialog would be nice.
Very minor as it's hardly a big imposition to paste and then edit to prune the preceding '_posts/'
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Very minor suggestion for the update_post workflow:
Allow for an (optional) preceding '_posts/' in the value for the update_post workflow post_name param.
Why?
If you go to the 'files' view for PR that might need an update, e.g.
https://github.com/wildfly/wildfly.org/pull/562/files
In the heading for single file in the PR the Github UI has a icon that lets you copy the file name, e.g.
_posts/2024-03-05-wildfly-gitops.md
Click that and the pasting the value into the update_post workflow dialog would be nice.
Very minor as it's hardly a big imposition to paste and then edit to prune the preceding '_posts/'
The text was updated successfully, but these errors were encountered: