Skip to content

[TC-003] - Add PrivateConst to gitignore#3676

Open
kdeakinstructure wants to merge 1 commit intomasterfrom
TC-003-data-seeding-private-data-hiding
Open

[TC-003] - Add PrivateConst to gitignore#3676
kdeakinstructure wants to merge 1 commit intomasterfrom
TC-003-data-seeding-private-data-hiding

Conversation

@kdeakinstructure
Copy link
Copy Markdown
Contributor

Put dataseeding PrivateConst file into gitignore to prevent unintentional push of hardcoded credentials.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 4, 2026

🧪 Unit Test Results


📊 Summary

  • Total Tests: 0
  • Failed: 0
  • Skipped: 0
  • Status: ⚠️ No test results found

Last updated: Mon, 04 May 2026 13:46:29 GMT

Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

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

Review Summary

This PR adds src/main/java/com/instructure/dataseeding/util/PrivateConst.kt to the .gitignore for the automation/dataseedingapi module — a straightforward and correct security hygiene change.

Findings:

  • No setup documentationautomation/dataseedingapi/readme.md has no mention of PrivateConst.kt or how developers should obtain/configure it. New contributors won't know this file is required for the build (compileKotlin depends on addPrivateData, which copies it from the private data vault), and they'll get a cryptic build failure without guidance.

What looks good:

  • The file is confirmed not currently tracked in git, so the .gitignore addition alone is sufficient (no git rm --cached needed).
  • Using src/main/java/... is intentional and matches where PrivateData.merge(project, "dataseeding") copies the file from the private vault — consistent with the existing src/main/java/com/instructure/soseedy gitignore pattern.
  • Protecting credentials/private constants from accidental commits is the right call, especially given this module builds against live Canvas API endpoints in CI.

The one suggestion worth addressing is adding a brief note to readme.md explaining that the build requires private data setup (pointing to the vault setup process), so developers hitting the PrivateData task failure know where to look.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 4, 2026

📊 Code Coverage Report

ℹ️ Student

  • PR Coverage: 42.48%
  • Master Coverage: N/A

ℹ️ Teacher

  • PR Coverage: 25.23%
  • Master Coverage: N/A

ℹ️ Pandautils

  • PR Coverage: 24.10%
  • Master Coverage: N/A

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.

2 participants