You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EGit provides a global setting to automatically include "Signed-off-by" messages in commits.
I propose adding an option to enable/disable this setting on a per-git-repository basis.
Motivation
In my workspace, I work on projects from various contexts (open-source, in-house, client projects, etc.), each with its own commit policies. Some projects require "Signed-off-by" messages, while for others, it’s unnecessary and just noise.
Currently, I have the global setting disabled and manually amend commits as needed. However, when switching between projects, I sometimes forget to adjust this, which leads to issues that I only notice after a failed PR or CI run. This can be time-consuming and frustrating.
Alternatives considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Wouldn't it make more sense to have this as a per-repository setting?
sebthom
changed the title
Allow enabling/disabling commit Signed-off-by on a per-project basis
Allow enabling/disabling commit Signed-off-by on a per-repository basis
Sep 9, 2024
Description
EGit provides a global setting to automatically include "Signed-off-by" messages in commits.
I propose adding an option to enable/disable this setting on a per-git-repository basis.
Motivation
In my workspace, I work on projects from various contexts (open-source, in-house, client projects, etc.), each with its own commit policies. Some projects require "Signed-off-by" messages, while for others, it’s unnecessary and just noise.
Currently, I have the global setting disabled and manually amend commits as needed. However, when switching between projects, I sometimes forget to adjust this, which leads to issues that I only notice after a failed PR or CI run. This can be time-consuming and frustrating.
Alternatives considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: