Skip to content

Add problem-report.html to .gitignore - #25417

Merged
wing328 merged 1 commit into
masterfrom
add-problem
Oct 26, 2026
Merged

wing328 merged 1 commit into
masterfrom
add-problem

Conversation

@wing328

@wing328 wing328 commented Oct 26, 2026 •

Copy link
Copy Markdown
Member

a follow up PR to #25416

PR checklist

  • Read the contribution guidelines.
  • Run the following to build the project and update samples:
    ./mvnw clean package || exit
    ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
    ./bin/utils/export_docs_generators.sh || exit
    
    (For Windows users, please run the script in WSL)
    Commit all changed files.
    This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
    These must match the expectations made by your contribution.
    You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
    IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@wing328
wing328 marked this pull request as ready for review October 26, 2026 03:24

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".gitignore">

<violation number="1" location=".gitignore:167">
P2: This rule ignores `problems-report.html`, but the PR requests ignoring `problem-detail.html`; generated `problem-detail.html` files will still be left untracked. Replace the filename with `problem-detail.html`.</violation>
</file>

Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic

Comment thread .gitignore
samples/client/petstore/swift3/**/SwaggerClientTests/Podfile.lock

# C#
**/problems-report.html

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P2: This rule ignores problems-report.html, but the PR requests ignoring problem-detail.html; generated problem-detail.html files will still be left untracked. Replace the filename with problem-detail.html.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At .gitignore, line 167:

<comment>This rule ignores `problems-report.html`, but the PR requests ignoring `problem-detail.html`; generated `problem-detail.html` files will still be left untracked. Replace the filename with `problem-detail.html`.</comment>

<file context>
@@ -164,6 +164,7 @@ samples/client/petstore/swift3/**/SwaggerClientTests/SwaggerClient.xcworkspace/x
 samples/client/petstore/swift3/**/SwaggerClientTests/Podfile.lock
 
 # C#
+**/problems-report.html
 *.csproj.user
 samples/client/petstore/csharp/SwaggerClient/IO.Swagger.userprefs
</file context>
Suggested change
**/problems-report.html
**/problem-detail.html

@wing328 wing328 changed the title add problem-detail.html to .gitignore Add problem-report.html to .gitignore Oct 26, 2026
@wing328
wing328 merged commit 75b3ca0 into master Oct 26, 2026
10 of 11 checks passed
@wing328
wing328 deleted the add-problem branch October 26, 2026 03:28
@wing328 wing328 added this to the 7.27.0 milestone Nov 2, 2026
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.

1 participant