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

Different bot responses #78

Open
1 task done
ftdgoodluck opened this issue May 16, 2024 · 2 comments
Open
1 task done

Different bot responses #78

ftdgoodluck opened this issue May 16, 2024 · 2 comments

Comments

@ftdgoodluck
Copy link
Collaborator

ftdgoodluck commented May 16, 2024

User story

As a participant of Race of Sloths (either maintainer or contributor) I want to receive different bot messages - either randomized or customized based on my achievements (e.g. streaks)

Acceptance criteria

  • Provide a clear way of storing messages' text in a separate file
  • Provide at least 3 different messages per potential message
  • Include messages for the following bot actions:
  • welcome messages- a message that the bot replies with once the PR is submitted to the race with include command
    • include_basic_message - a message with a basic bot response after the include command was called (or just after first time calling the bot inside a repo without any command - see user story Submitting pull request with a bot command #61
    • include_streak_message - same as above, customized with one of the best streaks that the contributor has at the moment
    • include_first_time_message - basic message customized for the first pull request from a particular contributor
    • all messages above can be edited after status update
  • score messages - a message that the bot sends after the maintainer/reviewer calls score command
    • correct_nonzero_scoring_message - a message within a normal workflow with a correct score above zero
    • correct_zero_scoring_message - same as above, but with a score of zero
    • correctable_scoring_message - a message with some score that is incorrect (e.g., not a Fibonacci number or the one that is above 13) that we can round up to the correct number
  • exclude messages - message after exclude command was called
    • correct_exclude_score_message - a message after a correct exclude command
  • pause messages
    • pause_message
    • unpause_message
  • merge messages - all messages that happen based on the merge events
    • merge_with_score_message - happens after the merge event if the score had been already provided
    • merge_without_score_message - happens after the merge event if the score had not been submitted
    • final_message - happens after 24 hours from the merge
  • error handling - all messages corresponding to the situations outside of the normal workflow
    • error_unknown_command_message - appears when it's not possible to parse a command (except this is a first call of the bot side the PR)
    • error_non_author_include_message - appears if the include command is not written by the original PR author
    • error_rights_violation_message - appears if the scoring/pause/unpause command was called by a person who is not a maintainer or reviewer
    • error_late_include_message - appears if the include command was submitted after the merge
    • error_late_scoring_message - appears if the scoring command was called after finalization (24 hours after merge)
    • pause_paused_message - appears once the repo is paused after another pause command was called
    • unpause_unpaused_message - appears once the repo had been unpaused and unpause command was called

Tasks

Preview Give feedback
  1. bot product
    ftdgoodluck
@akorchyn
Copy link
Collaborator

@ftdgoodluck:
I don't think we need to have:

  • pause_paused_message -> I think, bot should ignore anything after pause even new pause.
  • error_non_author_include_message -> don't need that

@ftdgoodluck
Copy link
Collaborator Author

Skipped different messages for MVP
Refer to #37 for different bot messages

@ftdgoodluck ftdgoodluck modified the milestones: [1] MVP, [2] post-MVP Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants