From 4366bf7c6d3acbcbbbdd681ab2698fcc0c380efd Mon Sep 17 00:00:00 2001 From: Jonathen Adkins Date: Mon, 1 Jun 2026 02:04:18 -0400 Subject: [PATCH] docs(bounty): specify the bounty label name and link to bounty issues Fixes testcontainers/testcontainers-java#6835 - Declare that bounty issues are tagged with the `bounty` label - Add direct link to the bounty label filter for discoverability --- docs/bounty.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/bounty.md b/docs/bounty.md index 56ee501062c..91721aac81f 100644 --- a/docs/bounty.md +++ b/docs/bounty.md @@ -20,7 +20,7 @@ As a sponsor, the process for creating a bounty is as follows: * Raise an issue, or find an existing issue that describes the bug or feature. * Start a discussion with the [Testcontainers org core maintainers](#organisation-core-maintainers) to agree that the issue is suitable for a bounty, and how much the reward amount should be. -* Once agreed, we will assign a label to the issue so that interested developers can find it. +- Once agreed, we will assign the `bounty` label to the issue so that interested developers can find it. You can view all open bounty issues at: https://github.com/testcontainers/testcontainers-java/labels/bounty Sponsors can create up to 1 or 3 bounties (according to tier) _per calendar month_ - i.e. the counter resets on the 1st of each month. If a sponsor does not use their full quota of bounty credits in a calendar month, they cannot be rolled over to the next month.