Bounty Bot Enhancement: Fixed Label Updates & Slack Integration #63
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.
π Changes Introduced:
β Implemented bounty tracking to update the existing bounty label instead of adding duplicates.
β Improved GitHub issue comments to update the existing bounty message instead of creating multiple comments.
β Sponsorship history tracking: Each userβs total sponsored developers count is tracked and displayed.
β Replaced SLACK_WEBHOOK_URL with SLACK_BOT_TOKEN for better Slack integration.
β Improved Slack notifications to reflect the updated bounty amount.
π₯ How It Works:
π Testing Done:
β Verified that bounties are correctly updated.
β Tested Slack notifications for accuracy.
β Ensured the GitHub comment updates correctly.
###Changes Made
-You need to manually add the SLACK_BOT_TOKEN and PERSONAL_ACCESS_TOKENS in secrets under actions
###Screenshots
###FIXES OWASP-BLT/BLT#3767