Skip to content

Add guidance to exclude Build and Cache Intel directories from Apache… #10969

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dewan-ahmed
Copy link
Collaborator

… RAT scans

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.

Description

  • Please describe your changes: Added documentation to help users configure the apache-rat-plugin to ignore Harness Build Intelligence and Cache Intelligence directories. These directories may be incorrectly flagged during license compliance checks. The update includes a list of paths to exclude and a sample pom.xml configuration snippet.
  • Jira/GitHub Issue numbers (if any): CI-17857
  • Preview links/images (Internal contributors only): __________________

PR lifecycle

We aim to merge PRs within one week or less, but delays happen sometimes.

If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.

PRs must meet these requirements to be merged:

  • Successful preview build.
  • Code owner review.
  • No merge conflicts.
  • Release notes/new features docs: Feature/version released to at least one prod environment.

@dewan-ahmed dewan-ahmed requested a review from smjt-h July 18, 2025 20:05
@dewan-ahmed dewan-ahmed self-assigned this Jul 18, 2025
@dewan-ahmed dewan-ahmed requested a review from nofarblue as a code owner July 18, 2025 20:05
@dewan-ahmed dewan-ahmed added the Content - gap / tech debt Content flag: This PR includes missing content or docs tech debt label Jul 18, 2025
@dewan-ahmed
Copy link
Collaborator Author

@rohanmaharjan100 Hey, I think the MDX parser might be treating the tag in the code block as an unclosed JSX element, even though it's inside triple backticks. This seems like a known MDX quirk with certain HTML-like tags. Could you confirm if that's what's causing the error? If so, maybe we can fix it by escaping the angle brackets or wrapping the snippet in a

{...}</pre> block.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content - gap / tech debt Content flag: This PR includes missing content or docs tech debt
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant