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

chore: gitignore generated next-env types #285

Conversation

riley-kohler
Copy link
Contributor

@riley-kohler riley-kohler commented Dec 16, 2024

Pull Request

Proposed Changes

Add next-env.d.ts to the gitignore file since it is autogenerated by next and should not be edited. This came up because next changed a reference link in that file and caused it to appear in the git's changed files.

Readiness Checklist

Author/Contributor

  • If documentation is needed for this change, has that been included in this pull request
  • run npm run lint and fix any linting issues that have been introduced
  • run npm run test and run tests
  • If publishing new data to the public (scorecards, security scan results, code quality results, live dashboards, etc.), please request review from @jeffrey-luszcz

Reviewer

  • Label as either bug, documentation, enhancement, infrastructure, maintenance, or breaking

@riley-kohler riley-kohler requested review from a team as code owners December 16, 2024 15:29
@riley-kohler riley-kohler force-pushed the gitignore_generated_next_env_types branch from c4758f7 to 85c654f Compare December 16, 2024 16:21
@riley-kohler riley-kohler merged commit 60073ac into github-community-projects:main Dec 16, 2024
6 checks passed
@riley-kohler riley-kohler deleted the gitignore_generated_next_env_types branch December 16, 2024 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants