Adding the points allocated to users in a PR comment

[LavanyaK235]

Adding the points allocated to users in a PR comment

[Copilot]

Pull request overview

This pull request introduces an automated contributor points tracking system that monitors PR activity and displays point allocations in PR comments. The system replaces a previous leaderboard-based approach with real-time point tracking directly on PRs, calculating points for reviews, approvals, merged PRs, and various bonus categories like bug fixes, security improvements, and documentation contributions.

Key Changes:

• Implements a comprehensive Python-based points tracking script that monitors multiple GitHub events (reviews, comments, PR lifecycle events)
• Replaces file-based leaderboard updates with dynamic PR comment updates showing live point tracking
• Expands point categories to include performance improvements, security fixes, and first-time contributor bonuses

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 18 comments.

File	Description
scripts/track_points.py	New 520-line Python script implementing the core points calculation logic, GitHub API integration, and PR comment management
scripts/config_points.yml	Updated configuration file expanding point categories from 4 to 10+ types, adding security, performance, and documentation bonuses
.github/workflows/points.yml	Refactored workflow to trigger on more event types (pull_request, issues, etc.) and execute the new tracking script instead of creating leaderboard PRs

[Copilot]

This GitHub Actions workflow file is missing the required Microsoft copyright header. According to repository standards, all source files including workflow YAML files should start with a copyright header before any other content.

[Copilot]

The error handling in this function catches all exceptions and returns an empty dictionary, which can mask genuine errors like authentication failures or network issues. This makes debugging difficult. Consider logging the specific error type and re-raising critical errors (like authentication failures) or at least returning an error indicator so the caller knows the request failed versus legitimately returning an empty result.

[Copilot]

This regex pattern has a potential issue: it will match partial words. For example, "closed" would match both "close" and "closed", and "fixing" would match "fix". While the current pattern uses word boundaries implicitly through the grouping, it could still match unintended variations. Consider using more precise patterns like r'\b(closes?|fixe[sd]|resolved?)\s*:?\s*#(\d+)' to ensure proper word boundaries.

Suggested change

	pattern = r'(?:close[sd]?|fix(?:e[sd])?|resolve[sd]?)\s*:?\s*#(\d+)'
	pattern = r'\b(closes?|fixe[sd]|resolved?)\b\s*:?\s*#(\d+)'

[Copilot]

This API call could cause rate limit issues for repositories with many PRs from a single user. The function limits to 100 PRs but doesn't implement pagination or rate limit handling. Additionally, checking if a user is a first-time contributor by fetching all their PRs is inefficient. Consider using the GitHub API's contributor statistics endpoint or checking the 'author_association' field which indicates 'FIRST_TIME_CONTRIBUTOR' status.

Suggested change

	def is_first_time_contributor(username: str, current_pr_number: int) -> bool:
	"""Check if the current PR is the user's first merged PR."""
	# Check if user has any other merged PRs (excluding current one)
	# Limit to recent 100 PRs to avoid API rate limits and performance issues
	try:
	search_result = github_api_request('GET', f'pulls?state=all&creator={username}&per_page=100')
	if isinstance(search_result, list):
	# Get all merged PRs excluding the current one
	other_merged_prs = [
	pr for pr in search_result
	if pr.get('merged_at') and pr.get('number') != current_pr_number
	]
	# First-time contributor if no other merged PRs exist
	return len(other_merged_prs) == 0
	except Exception as e:
	print(f"WARNING: Error checking first-time contributor status: {e}", file=sys.stderr)
	return False
	def is_first_time_contributor(pr_details: dict) -> bool:
	"""
	Check if the PR author is a first-time contributor using the 'author_association' field.
	Returns True if the author_association is 'FIRST_TIME_CONTRIBUTOR'.
	"""
	author_association = pr_details.get('author_association', '')
	return author_association.upper() == 'FIRST_TIME_CONTRIBUTOR'

[Copilot]

The variable name 'breakdown_source' is defined inside a conditional block but may be referenced outside of it. If 'has_security' is True but was set from PR labels (lines 210-221), the variable 'breakdown_source' is assigned on line 221. However, if the logic changes or the flow is unclear, this could lead to an UnboundLocalError. Consider initializing 'breakdown_source' before the conditional blocks to ensure it's always defined when used on line 227.

[Copilot]

The import statement for the 're' module is placed inside a function rather than at the top of the file with other imports. This violates PEP 8 style guidelines which recommend placing all imports at the top of the module. Move this import to line 38 with the other standard library imports.

[Copilot]

The function 'aggregate_contributor_points' receives a 'comments' parameter but never uses it. The function's docstring says it aggregates points from "reviews, comments, and pr_details", but the implementation only processes reviews and PR author points - not individual comments. Either implement comment processing (as documented in the module docstring on line 23) or remove the unused parameter and update the docstring.

[Copilot]

Variable pr_number is not used.

Suggested change

pr_number = pr_details.get('number')

[Copilot]

Variable result is not used.

Suggested change

	result = github_api_request('PATCH', f'issues/comments/{existing_comment_id}', {'body': body})
	github_api_request('PATCH', f'issues/comments/{existing_comment_id}', {'body': body})

[Copilot]

Variable result is not used.

Suggested change

	print(f"✅ Updated tracking comment (ID: {existing_comment_id})")
	else:
	# Create new comment
	result = github_api_request('POST', f'issues/{pr_number}/comments', {'body': body})
	print(f"✅ Created new tracking comment")
	if isinstance(result, dict) and 'id' in result:
	print(f"✅ Updated tracking comment (ID: {result['id']})")
	else:
	print(f"⚠️ Failed to update tracking comment (ID: {existing_comment_id}) - API response: {result}")
	else:
	# Create new comment
	result = github_api_request('POST', f'issues/{pr_number}/comments', {'body': body})
	if isinstance(result, dict) and 'id' in result:
	print(f"✅ Created new tracking comment (ID: {result['id']})")
	else:
	print(f"⚠️ Failed to create tracking comment - API response: {result}")

[rahuldevikar761]

Tokens are not safe if we developers run this, they can fetch the token.