Skip to content

Every contributor identified as new contributor in repo without issues #369

Open

Description

@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:

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

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

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

Activity

  1. github-actions commented on Oct 12, 2025

    @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.

  2. rcomer commented on Oct 15, 2025

    @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

  3. posquit0 commented on Dec 18, 2025

    @posquit0

    Same here.

  4. added a commit that references this issue on Jan 24, 2026
    e73de6f
  5. added a commit that references this issue on Sep 5, 2026
    eae58ce
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions