Cancelling Custom Bounty Requires Github URL
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 776
- PR merge metrics
- No merged PRs in 30d
Description
**Steps To Reproduce**
Steps to reproduce the behavior:
1. Create a custom bounty successfully
2. Cancel bounty
**Observed behavior**
Cancelling a custom bounty requires a github URL, but the custom bounties arent tied to github
**Expected behavior**
Cancelling custom bounty shouldnt require github related information
**Note:** This change should only take place for custom bounties.. bounties created off of github issues should remained unchanged
Contributor guide
Research direction
Start by tracing the custom bounty creation and cancellation flows, then compare their validation with the GitHub-backed bounty path. The change is done when custom bounties can be cancelled without GitHub information while GitHub-linked bounty cancellation remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100