Skip to content
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.

"Finding Vulnerabilities" step too long #34

Closed
brianamarie opened this issue Oct 9, 2018 · 1 comment · Fixed by #38
Closed

"Finding Vulnerabilities" step too long #34

brianamarie opened this issue Oct 9, 2018 · 1 comment · Fixed by #38

Comments

@brianamarie
Copy link
Contributor

"Finding Vulnerabilities" is just a lot of steps in the action phase. Is it too much? How could we break it up?

For adding a .gitignore, we have the bot create a branch. Should/could we do the same thing here, and have the bot create a branch, point out the part of the file that should be edited, and then post the instructions in the PR?

What if user's instruction was to check the dependencies, comment the proper version, and then the bot opened the the PR and the instructions were for the user to edit the file?

@brianamarie brianamarie mentioned this issue Oct 9, 2018
10 tasks
@brianamarie
Copy link
Contributor Author

What if user's instruction was to check the dependencies, comment the proper version, and then the bot opened the the PR and the instructions were for the user to edit the file?

As I go through the course again, this feels like the right amount in each step.

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

Successfully merging a pull request may close this issue.

1 participant