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

Add a help command for Meeseeks #20

Open
willingc opened this issue Feb 24, 2017 · 20 comments
Open

Add a help command for Meeseeks #20

willingc opened this issue Feb 24, 2017 · 20 comments

Comments

@willingc
Copy link

Add a simple help command that would print out the commands that are currently listed in the README.

@Carreau
Copy link
Contributor

Carreau commented Feb 24, 2017

@meeseeksdev help

1 similar comment
@Carreau
Copy link
Contributor

Carreau commented Feb 24, 2017

@meeseeksdev help

@lumberbot-app
Copy link
Contributor

lumberbot-app bot commented Feb 24, 2017

           The following commands are available:

           hello (Permission.none) 
  • open (Permission.write)
  • tag (Permission.admin)
  • untag (Permission.admin)
  • autopep8 (Permission.admin)
  • zen (Permission.none)
  • close (Permission.write)
  • merge (Permission.write)
  • migrate (Permission.admin)
  • take (Permission.write)
  • ready (Permission.write)
  • backport (Permission.admin)

@blink1073
Copy link
Collaborator

Thanks, @meeseeksdev[bot], good bot.

@Carreau
Copy link
Contributor

Carreau commented Feb 24, 2017

unnknown command ,

@Carreau
Copy link
Contributor

Carreau commented Feb 24, 2017

@meeseeksdev help

@lumberbot-app
Copy link
Contributor

lumberbot-app bot commented Feb 24, 2017

The following commands are available:

(Permission.admin) tag

  • (Permission.write) ready

  • (Permission.admin) untag

  • (Permission.admin) backport [to] {branch}

  • (Permission.admin) autopep8

  • (Permission.write) open

  • (Permission.write) close

  • (Permission.none) zen

  • (Permission.admin) migrate [to] {org}/{repo}

     Need to be admin on target repo. 
    
  • (Permission.write) merge

  • (Permission.none) hello

@willingc
Copy link
Author

@meeseeksdev zen

@Carreau
Copy link
Contributor

Carreau commented Feb 24, 2017

@meeseeksdev zen

It's broken right now I pushed a bad commit.

@willingc
Copy link
Author

Lol

@willingc
Copy link
Author

I find it oddly calming to talk with the bot ;-)

@Carreau
Copy link
Contributor

Carreau commented Feb 24, 2017

meeseeksdev help

@lumberbot-app
Copy link
Contributor

lumberbot-app bot commented Feb 24, 2017

The following commands are available:

@meeseeksdev ready {no arguments} (Permission.write)

Remove "waiting for author" tag, adds "need review" tag. Can also be issued
if you are the current PR author even if you are not admin. 

@meeseeksdev zen (Permission.none)

@meeseeksdev migrate [to] {org}/{repo} (Permission.admin)

Need to be admin on target repo. Replicate all comments on target repo and close current on.

@meeseeksdev open (Permission.write)

@meeseeksdev close (Permission.write)

@meeseeksdev untag tag[, tag, [...] ] (Permission.admin)

@meeseeksdev autopep8 (Permission.admin)

@meeseeksdev hello (Permission.none)

@meeseeksdev tag tag[, tag, [...] ] (Permission.admin)

@meeseeksdev backport [to] {branch} (Permission.admin)

@meeseeksdev merge (Permission.write)

@Carreau
Copy link
Contributor

Carreau commented Feb 24, 2017

@willingc You should be able to retry zen.

@willingc
Copy link
Author

@meeseeksdev[bot] zen

@lumberbot-app
Copy link
Contributor

lumberbot-app bot commented Feb 24, 2017

Zen of Pyton (pep 20)

>>> import this
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

@willingc
Copy link
Author

@meeseeksdev zen

@lumberbot-app
Copy link
Contributor

lumberbot-app bot commented Feb 24, 2017

Zen of Pyton (pep 20)

>>> import this
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

@willingc
Copy link
Author

Must meditate longer for more zen.

@Carreau
Copy link
Contributor

Carreau commented Feb 24, 2017

Must meditate longer for more zen.

If you have ideas for more zen, I'm happy to add it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants