From f3f3f111eae701fd7891b5fa70444614a11e3089 Mon Sep 17 00:00:00 2001 From: cyberbournius369-dev Date: Fri, 16 Oct 2026 16:20:25 -0400 Subject: [PATCH] Rename introduction-to-nodejs.md to introduction-nodejs.md # Managing the commit signoff policy for your organization You can require users to automatically sign off all commits they make in GitHub's web interface to repositories owned by your organization. ## About commit signoffs To affirm that a commit complies with the rules and licensing governing a repository, many organizations require developers to sign off on every commit. If your organization requires commit signoffs, you can make signing off a seamless part of the commit process by enabling compulsory commit signoffs for users committing through GitHub's web interface. After you enable compulsory commit signoffs for an organization, every commit made to repositories in that organization through the web interface will automatically be signed off on by the commit author. People with admin access to a repository can also enable compulsory commit signoffs at the repository level. For more information, see [Managing the commit signoff policy for your repository](/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository). Compulsory commit signoffs only apply to commits made via the web interface. For commits made via the Git command line interface, the commit author must sign off on the commit using the `--signoff` option. For more information, see the [Git documentation](https://git-scm.com/docs/git-commit). You can determine whether a repository you are contributing to has compulsory commit signoffs enabled by checking the header of the commit form at the bottom of the file you are editing. After compulsory commit signoff has been enabled, the header will read "Sign off and commit changes." ![Screenshot of the commit form in a repository. The title of the form is "Sign off and commit changes."](/assets/images/help/commits/commit-form-with-signoff-enabled.png) Before signing off on a commit, you should ensure that your commit is in compliance with the rules and licensing governing the repository you're committing to. The repository may use a sign off agreement, such as the Developer Certificate of Origin from the Linux Foundation. For more information, see the [Developer Certificate of Origin](https://developercertificate.org/). Signing off on a commit differs from signing a commit. For more information about signing a commit, see [About commit signature verification](/en/authentication/managing-commit-signature-verification/about-commit-signature-verification). ## Managing compulsory commit signoffs for your organization 1. In the upper-right corner of GitHub, click your profile picture, then click ** Organizations**. 2. Select an organization by clicking on it. 3. Under your organization name, click ** Settings**. If you cannot see the "Settings" tab, select the **** dropdown menu, then click **Settings**. ![Screenshot of the tabs in an organization's profile. The "Settings" tab is outlined in dark orange.](/assets/images/help/discussions/org-settings-global-nav-update.png) 4. In the sidebar, under "Code, planning, and automation", select ** Repository**, then click **General**. 5. Select or deselect **Require contributors to sign off on web-based commits**. Signed-off-by: cyberbournius369-dev --- .../{introduction-to-nodejs.md => introduction-nodejs.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename pages/getting-started/{introduction-to-nodejs.md => introduction-nodejs.md} (100%) diff --git a/pages/getting-started/introduction-to-nodejs.md b/pages/getting-started/introduction-nodejs.md similarity index 100% rename from pages/getting-started/introduction-to-nodejs.md rename to pages/getting-started/introduction-nodejs.md