Some comments in the test so that one can easily trace back the relevantĭiscussions after your patch gets committed, and the tickets get closed. Also, if some ticketsĪre relevant to the code that you’ve written, mention the ticket numbers in Regression test to validate the behavior that has beenįixed and to prevent the problem from arising again.
The code required to fix a problem or add a feature is an essential part.Make sure that any contribution you do fulfills at least the following “Action” near the bottom of the page, then click “Submit changes.” Claim the ticket by clicking the “assign to myself” radio button under.Or “DjangoProject Login” in the upper left of the ticket page. Log into your account, if you haven’t already, by clicking “GitHub Login”.If a ticket has been assigned for weeks or months withoutĪny activity, it’s probably safe to reassign it to yourself. Either find anotherīug/feature to work on, or contact the developer working on the ticket to Otherwise, somebody else may be working on this ticket. If it’s assigned to “nobody,” then it’s available to be claimed. To do this, look at the “Owned by” section of the ticket. If a ticket for this issue already exists, make sure nobody else hasĬlaimed it.If a ticket for this issue doesn’t exist yet, create one in our.If you have an account but have forgotten your password, you can Login using your GitHub account or create an account in our ticket.
If you have identified a contribution you want to make and you’re capable ofįixing it (as measured by your coding ability, knowledge of Django internalsĪnd time availability), claim it by following these steps:
Hence, our policy is for contributors to “claim” tickets in order to let otherĭevelopers know that a particular bug or feature is being worked on. Important to manage communication efficiently so that work doesn’t getĭuplicated and contributors can be as effective as possible. In an open-source project with hundreds of contributors around the world, it’s
0 kommentar(er)
