![]() ![]() Second, choose to Open the repository in your external editor. See this issue on GitHub Desktop for more information.įirst, in the list of the project pull requests (PR), click on the PR you'd like to modify. Unfortunately, this approach is complex because GitHub Desktop will change your branch name□. The second way is to fix the failing DCO check using GitHub Desktop. When you push again, the DCO check will pass. Then, just follow the instructions to fix DCOs in the commits in this PR. If you encounter a failing DCO check, go to your PR page and click on DCO details. The easiest way is to update your DCO via the command line. When that happens, the Pull Request (PR) could fail the automated DCO check, and be blocked from merging. How to fix a failing DCO checkĭevelopers could forget to include DCO sign-off messages in their commits. Download and install the chrome extension here. The email address DCO expects is your public email.Ĭhrome extension “DCO GitHub UI” could automatically add the correct signed-off message in every commit you make from the github web site. If it is on, the email address in your commit message should be the anonymous public email address that GitHub created for you. DCO via the GitHub web siteįor small code changes, the GitHub web editor is a very popular tool to edit and commit changes directly from your web browser.īefore you commit changes in the browser web form, just make sure you add Signed-off-by: username in the last line of your commit message.Ĭheck your GitHub email setting to see if the “Keep my email address private” toggle is turned on. Git adds your sign-off message in the commit message, and you contribution (commit) is now DCO compliant. ![]() $ git commit -s -m "This is my commit message" Now, every time you commit new code in git, just add a signoff statement via the -s flag. $ git config -global user.email you should use your own name and the email address associated with your GitHub user account. $ git config -global user.name "John Doe" The most popular way to do DCO is to sign off your username and email address in the git command line.įirst, configure your local git install. However, the CLA only needs to be signed once per developer per project. The CLA is a legal document that takes much more effort than a DCO to complete. Some projects require contributors to sign a CLA (Contributor License Agreement). In this article, I will teach you exactly how to sign a DCO for open source projects hosted on GitHub. It is a barrier for many potential open source contributors. However, signing the DCO could be confusing and error prone. When you contribute code to an open-source project, such as WasmEdge, you are often asked to sign a DCO (Developer Certificate of Origin) to ensure that the project has the proper rights to use your code. A Complete Guide to DCO for Open Source Developers
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |