LFX Insights
Blog Back to LF Insights

Code contributions & Collaborations ​

Insights tracks activity across platforms to capture the diverse ways individuals support open source projects. This activity is used to understand individual impact, engagement patterns, and participation across projects, communities, and platforms. Activities are grouped into two categories: Code contributions and Collaborations, highlighting both technical work and broader engagement.

1. Code contributions
Code contributions reflect meaningful technical and community-driven impact. They represent direct work that adds code or technical value to a project. This includes commits, pull requests, code reviews, and related technical activities.

2. Collaborations
Collaborations signal engagement or coordination rather than direct contributions, they capture non-code activities that support the project, including discussions, documentation, planning, and community engagement.

Learn more about the data sources we currently track.

NOTE

We’ve updated how Insights classifies activity. Previously, all meaningful activities were grouped under “Contributions”. We now distinguish between Code contributions and Collaborations to ensure that both technical and non-code work is recognized appropriately. Join the discussion here.

Tracked Code contribution types ​

Gerrit ​

  • changeset-created – Submitted a new changeset.
  • changeset-merged – Merged a code change into the main branch.
  • changeset-closed – Closed a code review.
  • changeset-abandoned – Abandoned a code change.
  • changeset_comment-created – Commented on a changeset.
  • patchset-created – Uploaded a new patchset for review.
  • patchset_comment-created – Commented on a patchset.
  • patchset_approval-created – Approved a patchset during review.

Git ​

  • authored-commit – Authored a Git commit in the default branch.
  • reviewed-commit – Reviewed a commit in the default branch.
  • tested-commit – Tested changes and marked them accordingly in the default branch.
  • co-authored-commit – Co-authored a commit with another user in the default branch.
  • informed-commit – Contributed ideas or guidance that led to a commit in the default branch.
  • influenced-commit – Indirectly influenced a commit’s creation in the default branch.
  • approved-commit – Approved a commit during code review in the default branch.
  • committed-commit – Committed changes to a repository in the default branch.
  • reported-commit – Reported an issue fixed by a commit in the default branch.
  • resolved-commit – Resolved an issue with a commit in the default branch.
  • signed-off-commit – Signed off on a commit for compliance/review in the default branch.

GitHub ​

  • pull_request-opened – Opened a new pull request.
  • pull_request-closed – Closed an existing pull request.
  • pull_request-review-requested – Requested a code review.
  • pull_request-reviewed – Reviewed a pull request.
  • pull_request-merged – Merged a pull request into the main branch.
  • pull_request-comment – Commented on a pull request.
  • authored-commit – Authored and pushed a commit in a pull request.

GitLab ​

  • merge_request-opened – Opened a new merge request.
  • merge_request-closed – Closed a merge request.
  • merge_request-review-requested – Requested a merge request review.
  • merge_request-review-approved – Approved a merge request.
  • merge_request-review-changes-requested – Requested changes on a merge request.
  • merge_request-merged – Merged a merge request.
  • merge_request-comment – Commented on a merge request.
  • authored-commit – Authored a commit in a merge request to a GitLab repo.

Tracked Collaboration types ​

Confluence ​

  • page-created – Created a new Confluence page.
  • page-updated – Edited or updated a Confluence page.
  • comment-created – Posted a comment on a page or blog post.
  • attachment-created – Uploaded a file or asset to a page.
  • blogpost-created – Published a new blog post.
  • blogpost-updated – Updated an existing blog post.
  • attachment – Attached a file to a page or blog post.

Discord ​

  • message – Sent a message in a channel or thread.
  • thread_started – Started a new thread in a channel.
  • thread_message – Replied within a thread.

GitHub ​

  • discussion-started – Started a new GitHub Discussion.
  • issues-opened – Opened a new issue.
  • issues-closed – Closed a previously opened issue.
  • issue-comment – Commented on an issue.
  • discussion-comment – Commented on a discussion.

GitLab ​

  • issues-opened – Opened a new issue.
  • issues-closed – Closed an existing issue.
  • issue-comment – Commented on an issue.

Groups.io ​

  • message – Sent a message to a mailing group or list.

Jira ​

  • issue-created – Created a new Jira issue or ticket.
  • issue-closed – Closed or resolved an issue.
  • issue-assigned – Assigned an issue to a user.
  • issue-updated – Updated issue status or content.
  • issue-comment-created – Added a new comment to an issue.
  • issue-comment-updated – Edited an existing comment.
  • issue-attachment-added – Added a file attachment to an issue.

Slack ​

  • message – Sent a message in a public or private Slack channel.

Stack Overflow ​

  • question – Asked a technical question.
  • answer – Provided an answer to someone else's question.