Add a step "open a blank issue"

[hectorsector]

The user installs Request info but seems to mostly be left hanging following that. Should we add a step where they trigger the app and use it as a new learning opportunity?

[a-a-ron]

Hey @hectorsector. Thanks for the review. We do, or at least it should. The steps are;

• user installs the app
• user edits the config.yml file
• if verified, bot merges the PR
• bot creates a new issue (which will now have the user's customized response) with the graceful_exit response

Were you referring to steps beyond this?

[hollenberry]

@hectorsector

For WIP, the user is currently left hanging. We can't really change the flow yet, unless inspiration strikes tomorrow.

For Request Info, @hiimbex graciously agreed to add some unique Learning Lab course functionality. Once behaviorbot/request-info#42 is merged, we should ideally see @a-a-ron 's flow with a minor amendment.

• user installs the app
• app greets user via PR comment
• lab prompts the user with new instructions
• user edits the config.yml file
• if verified, bot merges the PR
• bot creates a new issue (which will now have the user's customized response) with the graceful_exit response

[brianamarie]

I can see that there's some changes made to the behaviorbot functionality. Is the step for opening a blank issue still needed?

[hollenberry]

This reinforces the change to request_info's config file, but we might switch from that, so we can come back to this if that's not the case.

[brianamarie]

This is a step that exists now by opening a PR. #83 will build on this by having a pull request template tell the users not to change it.