refactopr: Refactor various classes to use GitProject instead of Project #1376
Conversation
Several classes have been refactored to replace the usage of the old Project class with the new GitProject class. This includes changes in fields, methods, and parameters, and affects multiple classes within the github-bot module. The changes bring more clarity and specificity to the naming and understanding of the project context.
![gitstream-cm[bot]](https://avatars.githubusercontent.com/in/230441?s=60&v=4){kind=small}
MartinWitt
changed the title
enforce_pr_title/enforce_pr_title • request change and add this comment: Type must be one of the following:
label_deleted_files/label_deleted_files • add label percent_new_code/percent_new_code • add comment provide_estimated_time_to_review/estimated_time_to_review • add label review_todo_comments/review_todo_comments • request change and add this comment: To activate these actions - merge this PR into the main branch Learn more on the gitStream Docs |
Qodana Community for JVMIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/[email protected]
with:
upload-result: trueContact Qodana teamContact us at [email protected]
|
Several classes have been refactored to replace the usage of the old Project class with the new GitProject class. This includes changes in fields, methods, and parameters, and affects multiple classes within the github-bot module. The changes bring more clarity and specificity to the naming and understanding of the project context.