Skip to content

Commit 07e079a

Browse files
committed
chore: remove comment
1 parent 51fb3be commit 07e079a

1 file changed

Lines changed: 0 additions & 82 deletions

File tree

services/apps/git_integration/src/crowdgit/services/maintainer/maintainer_service.py

Lines changed: 0 additions & 82 deletions
Original file line numberDiff line numberDiff line change
@@ -220,88 +220,6 @@ def get_extraction_prompt(self, filename: str, content_to_analyze: str) -> str:
220220
{content_to_analyze}
221221
---
222222
"""
223-
# return f"""
224-
# You are a highly efficient AI assistant designed for one task: to quickly parse repository files and extract maintainer information into a structured JSON format. Your priority is speed and accuracy.
225-
226-
# <task_rules>
227-
# 1. **Primary Goal**: Analyze the `<content_to_analyze>` and extract a list of individual maintainers. Do not extract teams or organizations.
228-
# 2. **Input Context**: You are given a `<filename>` and the file's `<content_to_analyze>`.
229-
# 3. **Output Format**: You MUST return a single JSON object and nothing else.
230-
# - On success (maintainers found): `{{"info": [list_of_maintainer_objects]}}`
231-
# - On failure (no maintainers found, or content only refers to a group): `{{"error": "not_found"}}`
232-
# </task_rules>
233-
234-
# <extraction_schema>
235-
# For each individual person you find, create a JSON object with these exact fields:
236-
237-
# - `github_username`: Find using common patterns like `@username`, `github.com/username`, `Name (@username)`, or from emails (`123+user@users.noreply.github.com`). If a username cannot be found in the text, use the string "unknown".
238-
239-
# - `name`: The person's full name.
240-
241-
# - `title`: The person's role (max two words). It must relate to ownership or maintainership (e.g., "Core Maintainer", "Lead Reviewer"), not a generic job title like "Software Engineer". Avoid filler words like 'project' or 'active'.
242-
243-
# - `normalized_title`: Must be exactly "maintainer" or "contributor". If the role is ambiguous, use the `<filename>` as the primary hint. For example, a file named `MAINTAINERS` or `CODEOWNERS` implies "maintainer", while `CONTRIBUTORS` implies "contributor".
244-
# </extraction_schema>
245-
246-
# <examples>
247-
# <example>
248-
# <context>
249-
# <filename>CODEOWNERS</filename>
250-
# <content_to_analyze>
251-
# # Project Lead: Jane Doe (@jane-doe-gh)
252-
# # Core Maintainer is John Smith (123+jsmith@users.noreply.github.com).
253-
# </content_to_analyze>
254-
# </context>
255-
# <expected_output>
256-
# {{
257-
# "info": [
258-
# {{
259-
# "github_username": "jane-doe-gh",
260-
# "name": "Jane Doe",
261-
# "title": "Project Lead",
262-
# "normalized_title": "maintainer"
263-
# }},
264-
# {{
265-
# "github_username": "jsmith",
266-
# "name": "John Smith",
267-
# "title": "Core Maintainer",
268-
# "normalized_title": "maintainer"
269-
# }}
270-
# ]
271-
# }}
272-
# </expected_output>
273-
# </example>
274-
# <example>
275-
# <context>
276-
# <filename>CONTRIBUTORS.md</filename>
277-
# <content_to_analyze>
278-
# Thanks to our amazing contributor, Alex Ray! Find their work on GitHub under 'alex-ray-dev'.
279-
# </content_to_analyze>
280-
# </context>
281-
# <expected_output>
282-
# {{
283-
# "info": [
284-
# {{
285-
# "github_username": "alex-ray-dev",
286-
# "name": "Alex Ray",
287-
# "title": "Contributor",
288-
# "normalized_title": "contributor"
289-
# }}
290-
# ]
291-
# }}
292-
# </expected_output>
293-
# </example>
294-
# </examples>
295-
296-
# <context>
297-
# <filename>{filename}</filename>
298-
# <content_to_analyze>
299-
# {content_to_analyze}
300-
# </content_to_analyze>
301-
# </context>
302-
303-
# Return only the final JSON object.
304-
# """
305223

306224
async def analyze_file_content(self, maintainer_filename: str, content: str):
307225
prompt = self.get_extraction_prompt(maintainer_filename, content)

0 commit comments

Comments
 (0)