Skip to content
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

Merged
merged 5 commits into from
Dec 30, 2020
Merged

DOC: chat-ops #38754

merged 5 commits into from
Dec 30, 2020

Conversation

1nF0rmed
Copy link
Contributor

@1nF0rmed 1nF0rmed commented Dec 28, 2020

  • closes DOC: chat-ops #38726
  • tests added / passed
  • passes black pandas
  • passes git diff upstream/master -u -- "*.py" | flake8 --diff
  • Added documentation for @githubactions pre-commit
  • Added documentation for @meeseeksdev backport

@1nF0rmed
Copy link
Contributor Author

@githubactions pre-commit

Copy link
Member

@rhshadrach rhshadrach left a 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?

doc/source/development/contributing.rst Outdated Show resolved Hide resolved
doc/source/development/contributing.rst Outdated Show resolved Hide resolved

on that pull request. This will trigger a workflow which will autofix formatting errors.

Backporting (optional)
Copy link
Contributor

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?)

Copy link
Member

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?

Copy link
Contributor Author

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?

Copy link
Member

@MarcoGorelli MarcoGorelli Dec 29, 2020

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

@jreback jreback added the Docs label Dec 28, 2020
you make a pull request. If there is a scenario where any of these checks fail then you
can comment::

@githubactions pre-commit
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be

Suggested change
@githubactions pre-commit
@github-actions pre-commit

, I missed out the - in the issue

@1nF0rmed
Copy link
Contributor Author

I'll make these changes and commit ASAP

@MarcoGorelli
Copy link
Member

ASAP

🤣 thanks, but there's no hurry

Comment on lines 154 to 163
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.
Copy link
Member

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

@jreback jreback added this to the 1.3 milestone Dec 29, 2020
@jreback
Copy link
Contributor

jreback commented Dec 29, 2020

thanks @1nF0rmed

if any more comments @rhshadrach @MarcoGorelli

@jreback jreback merged commit e85d078 into pandas-dev:master Dec 30, 2020
@jreback
Copy link
Contributor

jreback commented Dec 30, 2020

thanks @1nF0rmed

luckyvs1 pushed a commit to luckyvs1/pandas that referenced this pull request Jan 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DOC: chat-ops
4 participants