dev → main: extraction that quotes its evidence, graph paths in chat, rules that compute, the ontology as tables - #594

There are 4 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 <authoremail@example.com> 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.

Preferred method: Commit author adds a DCO remediation commit

A DCO Remediation Commit contains special text in the commit message that applies a missing Signed-off-by line in a subsequent commit. The primary benefit of this method is that the project’s history does not change, and there is no risk of breaking someone else’s work.

These authors can unblock this PR by adding a new commit to this branch with the following text in their commit message:

Ben Younes <benyounes.ousama@gmail.com>

DCO Remediation Commit for Ben Younes <benyounes.ousama@gmail.com>

I, Ben Younes <benyounes.ousama@gmail.com>, hereby add my Signed-off-by to this commit: 357d4ac45f22d85db5339c68789d449e7c1e14ef
I, Ben Younes <benyounes.ousama@gmail.com>, hereby add my Signed-off-by to this commit: 932c3ba8d4fceef0387b33dd9247245f20df7c5c
I, Ben Younes <benyounes.ousama@gmail.com>, hereby add my Signed-off-by to this commit: ad8517f611fc4575bf5d2838c63c5aea600524e3
I, Ben Younes <benyounes.ousama@gmail.com>, hereby add my Signed-off-by to this commit: 526fc9153370cc4215965547e375627e22950308

Signed-off-by: Ben Younes <benyounes.ousama@gmail.com>

Please note: You should avoid adding empty commits (i.e., git commit -s --allow-empty), because these will be discarded if someone rebases the branch / repo.

Alternate method: An employer adds a DCO Remediation Commit

If the contents of this commit were contributed on behalf of a third party (generally, the author’s employer), an authorized individual may add a Third-Party DCO Remediation Commit. This may be necessary if the original author is unavailable to add their own DCO Remediation Commit to this branch.

If you are about to add a Third-Party DCO Remediation Commit under DCO section (b) or (c), be sure you are authorized by your employer to take this action. Generally speaking, maintainers and other project contributors cannot sign off on behalf of project contributors, unless there is some relationship which permits this action. It is your responsibility to verify this.

This PR can be unblocked by an authorized third party adding one or more new commits to this branch with the following text in the commit message. Replace YOUR_COMPANY with your company name, YOUR_NAME with the name of the authorized representative, and YOUR_EMAIL with the representative’s email address.

For the sake of clarity, please use a separate commit per author:

On behalf of Ben Younes <benyounes.ousama@gmail.com>

Third-Party DCO Remediation Commit for Ben Younes <benyounes.ousama@gmail.com>

On behalf of Ben Younes <benyounes.ousama@gmail.com>, I, YOUR_NAME <YOUR_EMAIL>, hereby add my Signed-off-by to this commit: 357d4ac45f22d85db5339c68789d449e7c1e14ef
On behalf of Ben Younes <benyounes.ousama@gmail.com>, I, YOUR_NAME <YOUR_EMAIL>, hereby add my Signed-off-by to this commit: 932c3ba8d4fceef0387b33dd9247245f20df7c5c
On behalf of Ben Younes <benyounes.ousama@gmail.com>, I, YOUR_NAME <YOUR_EMAIL>, hereby add my Signed-off-by to this commit: ad8517f611fc4575bf5d2838c63c5aea600524e3
On behalf of Ben Younes <benyounes.ousama@gmail.com>, I, YOUR_NAME <YOUR_EMAIL>, hereby add my Signed-off-by to this commit: 526fc9153370cc4215965547e375627e22950308

Signed-off-by: YOUR_NAME <YOUR_EMAIL>

Least preferred method: 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~67 --signoff
3. Force push your changes to overwrite the branch: git push --force-with-lease origin dev

Summary

Commit sha: 357d4ac, Author: Ben Younes, Committer: GitHub; Expected "Ben Younes benyounes.ousama@gmail.com", but got "Ben Younes 2910651+ousamabenyounes@users.noreply.github.com".
Commit sha: 932c3ba, Author: Ben Younes, Committer: GitHub; Can not find "Ben Younes benyounes.ousama@gmail.com", in ["Ben Younes 2910651+ousamabenyounes@users.noreply.github.com", "WaylandYang wayland0916@gmail.com", "Ben Younes 2910651+ousamabenyounes@users.noreply.github.com", "WaylandYang wayland0916@gmail.com"].
Commit sha: ad8517f, Author: Ben Younes, Committer: GitHub; Expected "Ben Younes benyounes.ousama@gmail.com", but got "Ben Younes 2910651+ousamabenyounes@users.noreply.github.com".
Commit sha: 526fc91, Author: Ben Younes, Committer: GitHub; Expected "Ben Younes benyounes.ousama@gmail.com", but got "Ben Younes 2910651+ousamabenyounes@users.noreply.github.com".