Skip running gradle checks on release notes

[gaiksaya]

Description

Running gradle check on release notes does not provide any value but instead adds a huge overhead while merging PRs during release cycle. Had to wait for 2+ hours during 2.13.0 while creating RC as release notes if one of the entrance criteria to start the release window.
Please let me know if we should include all .mdfiles as well .github directory to this list as well.

Related Issues

opensearch-project/opensearch-build#4562

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[reta]

@gaiksaya see please #13085

[github-actions]

✅ Gradle check result for 35f2eee: SUCCESS

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.47%. Comparing base (b15cb0c) to head (8e0d3ff).
Report is 246 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #13477      +/-   ##
============================================
+ Coverage     71.42%   71.47%   +0.04%     
- Complexity    59978    60975     +997     
============================================
  Files          4985     5050      +65     
  Lines        282275   286804    +4529     
  Branches      40946    41550     +604     
============================================
+ Hits         201603   204979    +3376     
- Misses        63999    64847     +848     
- Partials      16673    16978     +305     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kotwanikunal]

@reta I think this makes it easier coming in from a strictly onlyContains(*) POV.
We can keep adding path/files to this as we find fit.
Thanks @gaiksaya for moving this along :)

[gaiksaya]

@kotwanikunal @reta Can I merge this as is or do you have recommendations on more things to add under paths-ignore?

[kotwanikunal]

.github, *.md would be straightaway useful as well.

[reta]

@kotwanikunal @reta Can I merge this as is or do you have recommendations on more things to add under paths-ignore?

I think the intention was to cover larger scope of changes that do not require check runs, leaving it up to @kotwanikunal since he was working on it.

[gaiksaya]

.github, *.md would be straightaway useful as well.

Done!

[github-actions]

❌ Gradle check result for 8e0d3ff: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for 8e0d3ff: SUCCESS

[gaiksaya]

Added backport 2x label. @rishabh6788 @bbarani leaving upto you if you want this in 2.14 branch. Might help save sometime (actually hours) for things like release notes and .md changes.

[bbarani]

@rishabh6788 Lets backport this to 2.14 branch.