Is that PHP 7.4 compatible?

Is that PHP 7.4 compatible?

Ah no, sorry. I'll adjust.

I'm not sure why my commits aren't signed. I signed them, and saw the signage in the commit message.

The DCO bot wants you to add Signed-off-by to your commit message, not a digital signature.

The DCO bot wants you to add Signed-off-by to your commit message, not a digital signature.

I'm aware. That didn't work and I don't know why.

👉🏻 https://github.com/fairpm/fair-plugin/pull/34/checks

👉🏻 https://github.com/fairpm/fair-plugin/pull/34/checks

I read that, and followed those instructions. That's how we got here.

@topher1kenobe The problem is you have two commits that weren’t signed off. I had the same problem when I messed up signing one and the whole PR held on to it.

Did you do this part? The force push was the only way to fix it.

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~4 --signoff
3. Force push your changes to overwrite the branch: git push --force-with-lease origin issue-33/allow-null-input-on-dashboard

@topher1kenobe The problem is you have two commits that weren’t signed off. I had the same problem when I messed up signing one and the whole PR held on to it.

Did you do this part? The force push was the only way to fix it.

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](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally).

2. In your local branch, run: `git rebase HEAD~4 --signoff`

3. Force push your changes to overwrite the branch: `git push --force-with-lease origin issue-33/allow-null-input-on-dashboard`

I had tried this once before, but I've done it again. We'll see if it works.

That worked! Looks like it never properly force pushed. No worries, git can get weird.

I’m doing a scan to see how common this error is in plugins. Regardless I think this is a good fix. Should/can we toss in a “doing it wrong” notice for the devs?

Docblock change and null handling is mmissing.