Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clean: Clarify the version of Codacy configuration file considered DOCS-677 #2102

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

claudiacarpinteiro
Copy link
Contributor

@claudiacarpinteiro claudiacarpinteiro commented May 9, 2024

@claudiacarpinteiro claudiacarpinteiro self-assigned this May 9, 2024
Copy link
Contributor

github-actions bot commented May 9, 2024

Overall readability score: 53.83 (🔴 -0.01)

File Readability
codacy-configuration-file.md 56.9 (🔴 -1.61)
View detailed metrics

🟢 - Shows an increase in readability
🔴 - Shows a decrease in readability

File Readability FRE GF ARI CLI DCRS
codacy-configuration-file.md 56.9 36.69 10.11 13 12.76 6.73
  🔴 -1.61 🔴 -8.87 🔴 -0.01 🔴 -0.2 🟢 +0 🟢 +0.05

Averages:

  Readability FRE GF ARI CLI DCRS
Average 53.83 42.5 10.89 12.45 12.56 7.91
  🔴 -0.01 🔴 -0.04 🟢 +0 🟢 +0 🟢 +0 🟢 +0
View metric targets
Metric Range Ideal score
Flesch Reading Ease 100 (very easy read) to 0 (extremely difficult read) 60
Gunning Fog 6 (very easy read) to 17 (extremely difficult read) 8 or less
Auto. Read. Index 6 (very easy read) to 14 (extremely difficult read) 8 or less
Coleman Liau Index 6 (very easy read) to 17 (extremely difficult read) 8 or less
Dale-Chall Readability 4.9 (very easy read) to 9.9 (extremely difficult read) 6.9 or less

Comment on lines +21 to +26
- Codacy uses the version of the configuration file **in the branch being analyzed**. For example, if you open a pull request that includes changes to the Codacy configuration file, the analysis results take those changes into account. However, if the Codacy configuration file **in the default branch** includes settings to [ignore files](#syntax-for-ignoring-files):

- The analysis results of any branch always take the ignore settings defined **in the default branch** into account.
- The ignore settings of the Codacy configuration file **in the branch being analyzed** are cumulative and don't override the settings defined **in the default branch**.

For example, if the Codacy configuration file **in the default branch** excludes file A from analysis, that file will be excluded from analysis **in any branch being analyzed** even if you remove that rule from the Codacy configuration file in that branch.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nicklem I could use your help here! 🙏
I believe the content is technically correct (see the thread), but it seems a bit verbose. Another pair of expert eyes can probably make it simpler. 😅 👀

Copy link
Contributor

@nicklem nicklem May 10, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a tough one, definitely! Here are a couple of ideas. We can discuss these later (or even during the offiste!)

  • If a pull request modifies the Codacy configuration file, Codacy uses the updated configuration file to analyze that pull request. However, this does not apply to ignored files (see next point).
  • If a pull request removes an ignored path from the Codacy configuration file, any matching files will stay ignored until that pull request is merged into the default branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants