Skip to content

Add a help command for Meeseeks #20

Open

Description

@willingc

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

Activity

  1. Carreau commented on Feb 24, 2017

    @Carreau
    Member
  2. Carreau commented on Feb 24, 2017

    @Carreau
    Member
  3. lumberbot-app commented on Feb 24, 2017

    @lumberbot-app
    Contributor
               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)
  4. blink1073 commented on Feb 24, 2017

    @blink1073
    Collaborator

    Thanks, @meeseeksdev[bot], good bot.

  5. Carreau commented on Feb 24, 2017

    @Carreau
    Member

    unnknown command ,

  6. Carreau commented on Feb 24, 2017

    @Carreau
    Member
  7. lumberbot-app commented on Feb 24, 2017

    @lumberbot-app
    Contributor

    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

  8. willingc commented on Feb 24, 2017

    @willingc
    Author
  9. Carreau commented on Feb 24, 2017

    @Carreau
    Member

    @meeseeksdev zen

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

  10. willingc commented on Feb 24, 2017

    @willingc
    Author

    Lol

  11. willingc commented on Feb 24, 2017

    @willingc
    Author

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

  12. Carreau commented on Feb 24, 2017

    @Carreau
    Member

    meeseeksdev help

  13. lumberbot-app commented on Feb 24, 2017

    @lumberbot-app
    Contributor

    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)

  14. Carreau commented on Feb 24, 2017

    @Carreau
    Member

    @willingc You should be able to retry zen.

  15. willingc commented on Feb 24, 2017

    @willingc
    Author

    @meeseeksdev[bot] zen

  16. lumberbot-app commented on Feb 24, 2017

    @lumberbot-app
    Contributor

    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!
    
  17. willingc commented on Feb 24, 2017

    @willingc
    Author
  18. lumberbot-app commented on Feb 24, 2017

    @lumberbot-app
    Contributor

    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!
    
  19. willingc commented on Feb 24, 2017

    @willingc
    Author

    Must meditate longer for more zen.

  20. Carreau commented on Feb 24, 2017

    @Carreau
    Member

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions