Feat/soroban uint32 #1691
Feat/soroban uint32 #1691
Check failed
There are 8 commits incorrectly signed off, the check did not pass.
Summary
| Sha | Message | Pass or fail reason | |
|---|---|---|---|
| 🟢 | 323c289 | Success adding support to uint32 type for soroban ... | Valid sign-off found |
| 🔴 | ff8f788 | added support for uint32 in Soroban. | Sign-off not found |
| 🔴 | 46d08d1 | added unit test and integration test. | Sign-off not found |
| 🔴 | f76eb3f | as per pr edit. | Sign-off not found |
| 🔴 | 1362b78 | removed .DS_Store | Sign-off not found |
| 🟢 | c1fc2a5 | Success adding support to uint32 type for soroban ... | Valid sign-off found |
| 🔴 | d90c6c1 | Save local changes before merging upstream/main | Sign-off not found |
| 🔴 | 2c489b6 | restored | Sign-off not found |
| 🔴 | 75f528c | Ignored and Removed .DS_Store files | Sign-off not found |
| 🔴 | b68f164 | Ignored and Removed .DS_Store files | Sign-off not found |
Errors details
Sign-off not found
No sign-off was found in the commit message. This usually means that the author or committer of this commit failed to include a Signed-off-by line in the commit message. In some cases, this error can also be raised if the sign-off is not in the correct format.
To avoid having pull requests blocked in the future, always include a Signed-off-by: User1 <[email protected]> line in every commit message. You can also do this automatically by using the -s flag (i.e., git commit -s).
How to fix missing or invalid sign-offs
Option 1: add remediation commit
Remediation commits are not allowed for this repository. For more details about how to enable them, please see the documentation.
Option 2: fix commits without sign-off
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").
Warning
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
To add your Signed-off-by line to every commit in this branch:
- Ensure you have a local copy of your branch by checking out the pull request locally via command line.
- In your local branch, run:
git rebase HEAD~10 --signoff - Force push your changes to overwrite the branch:
git push --force-with-lease origin feat/soroban-uint32