Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOC] Character filters - Pattern replace #8347

doc: updates to formatting, explanation of regex

203a48a
Select commit
Loading
Failed to load commit list.
Closed

[DOC] Character filters - Pattern replace #8347

doc: updates to formatting, explanation of regex
203a48a
Select commit
Loading
Failed to load commit list.
DCO / DCO required action Oct 17, 2024 in 0s

DCO

There are 6 commits incorrectly signed off. This means that the author(s) of these commits failed to include a Signed-off-by line in their commit message.

To avoid having PRs blocked in the future, always include Signed-off-by: Author Name <[email protected]> in every commit message. You can also do this automatically by using the -s flag (i.e., git commit -s).

Here is how to fix the problem so that this code can be merged.


Rebase the branch

If you have a local git environment and meet the criteria below, one option is to rebase the branch and add your Signed-off-by lines in the new commits. Please note that if others have already begun work based upon the commits in this branch, this solution will rewrite history and may cause serious issues for collaborators (described in the git documentation under "The Perils of Rebasing").

You should only do this if:

  • You are the only author of the commits in this branch
  • You are absolutely certain nobody else is doing any work based upon this branch
  • There are no empty commits in the branch (for example, a DCO Remediation Commit which was added using --allow-empty)

To add your Signed-off-by line to every commit in this branch:

  1. Ensure you have a local copy of your branch by checking out the pull request locally via command line.
  2. In your local branch, run: git rebase HEAD~26 --signoff
  3. Force push your changes to overwrite the branch: git push --force-with-lease origin addition-pattern-replace-character-filter

Summary

Commit sha: 5cc4d31, Author: Ian Menendez, Committer: [email protected]; Can not find "Ian Menendez [email protected]", in ["Ian Menendez [email protected]", "kolchfa-aws [email protected]", "Ian Menendez [email protected]", "kolchfa-aws [email protected]"].
Commit sha: 7d956b7, Author: kolchfa-aws, Committer: [email protected]; Expected "kolchfa-aws [email protected]", but got "Fanit Kolchina [email protected]".
Commit sha: 9fffa33, Author: kolchfa-aws, Committer: [email protected]; Expected "kolchfa-aws [email protected]", but got "Fanit Kolchina [email protected]".
Commit sha: c8de4f7, Author: Naarcha-AWS, Committer: [email protected]; Can not find "Naarcha-AWS [email protected]", in ["Archer [email protected]", "Archer [email protected]", "Archer [email protected]", "Archer [email protected]", "Archer [email protected]", "Archer [email protected]", "Archer [email protected]"].
Commit sha: cd6dd70, Author: Naarcha-AWS, Committer: [email protected]; Can not find "Naarcha-AWS [email protected]", in ["Archer [email protected]", "Archer [email protected]", "Archer [email protected]", "Archer [email protected]", "Archer [email protected]", "Archer [email protected]", "Archer [email protected]", "Archer [email protected]", "Archer [email protected]", "Archer [email protected]"].
Commit sha: a488b45, Author: Nathan Bower, Committer: [email protected]; Expected "Nathan Bower [email protected]", but got "natebower [email protected]".