Create bounty form #113
Merged
Create bounty form #113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
* Move external links to a single file * Validate form fields in `/bounty/create` * Validate form fields in `/bounty/<id>/sponsor` * Validate form fields in `/bounty/<id>/exploit`
|
Ready for review, @guidanoli ! 😉 |
|
This needs a rebase. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to call a google form when users click on Create bounty button, given that currently we are not able to allow users to create their bounties permissionlessly.
@guidanoli I will create it as draft to wait until you merge the one related to form validation, because your PR has a file on /utils to add the URLs. The google form url should be there also.