Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Heyo Gitcoiners! With an entire city of hackers, coders and blockchain innovators relocated on our platform, the atmosphere is just buzzing with crea…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
We would like to start enforcing the format of `TODO(1234)` for TODOs in our code where 1234 represents the github issue associated with that task.
The requirements for this issue are to add a script to travis that will complain if there are any issues incorrectly formatted. See [scripts/check_gazelle.sh](https://github.com/prysmaticlabs/prysm/blob/master/scripts/check_gazelle.sh) for inspiration.
A prerequesite to submitting a fix for this issue would be that all of the TODOs are correctly formatted. Creating issues for the existing TODOs should be done by the original code owner (see git blame). The assignee of this issue should ping original owners to create issues for the respective TODOs.
I've written a quick regex and there are many TODOs that need an issue or need to be deleted.
grep -PinH '(?