-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
New issue
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
DOC: chat-ops #38754
DOC: chat-ops #38754
Conversation
@githubactions pre-commit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! I assume meeseeksdev
can only be used by someone with write permissions; remarks should be made to that effect. I'm also wondering if there should be some language around backporting to the effect of "you shouldn't be using this unless you really know otherwise". Thoughts here @simonjayhawkins?
|
||
on that pull request. This will trigger a workflow which will autofix formatting errors. | ||
|
||
Backporting (optional) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should only be in the maintainers section (i think we have one?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, doc/source/development/maintaining.rst - @1nF0rmed could you move this over there please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does that include the backporting section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, the whole part about @meeseeksdev backport
should be in the maintainers section
you make a pull request. If there is a scenario where any of these checks fail then you | ||
can comment:: | ||
|
||
@githubactions pre-commit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be
@githubactions pre-commit | |
@github-actions pre-commit |
, I missed out the -
in the issue
I'll make these changes and commit ASAP |
🤣 thanks, but there's no hurry |
Autofixing formatting errors | ||
---------------------------- | ||
|
||
We use several styling checks (e.g. ``black``, ``flake8``, ``isort``) which are run after | ||
you make a pull request. If there is a scenario where any of these checks fail then you | ||
can comment:: | ||
|
||
@github-actions pre-commit | ||
|
||
on that pull request. This will trigger a workflow which will autofix formatting errors. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for being unclear - this part can go in contributing.rst
, it's the backporting section that should go in maintaining.rst
thanks @1nF0rmed if any more comments @rhshadrach @MarcoGorelli |
thanks @1nF0rmed |
black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff
@githubactions pre-commit
@meeseeksdev backport