Every contributor identified as new contributor in repo without issues

[jacobtylerwalls]

Hi, thanks for this tool.

In the repository I work on, we've disabled GitHub Issues.

In 3.1 (and likely since v2), we've found that all contributors are identified as new contributors.

I suppose that's because isFirstIssue returns true:

first-interaction/__tests__/main.test.ts

Line 178 in ee654d9

it('Returns true if no issues are present', async () => {

And that check must be false to be identified as an existing contributor:

first-interaction/src/main.ts

Lines 40 to 42 in 1c46889

	// Check if this is the user's first contribution.
	if (!(await isFirstIssue(octokit)) && !(await isFirstPullRequest(octokit)))
	return core.info('Skipping...Not First Contribution')

[github-actions]

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

[rcomer]

I have been playing with this in my fork of Matplotlib which, until today, also had issues switched off. Even after I turn issues on and open one, I still get the "new contributor" message on PRs.
https://github.com/rcomer/matplotlib/issues?q=is%3Aissue%20is%3Apr%20state%3Aopen