Skip to content

Conversation

@alexfmpe
Copy link
Contributor

Unclear why two steps are required for a single opt-in.

It has happened on multiple projects that I uncomment the flag but forget to also toggle it.

An alternative is leaving as a comment with = true but the approach here has the advantage that changes upstream to the attribute paths will trigger eval errors/warnings when they happen, not when the flag is next uncommented, minimizing distance between cause and effect.

I have:

  • Based work on latest develop branch
  • Followed the contribution guide
  • Looked for lint in my changes with hlint . (lint found code you did not write can be left alone)
  • Run the test suite: $(nix-build -A selftest --no-out-link)
  • Updated the changelog
  • (Optional) Run CI tests locally: nix-build release.nix -A build.x86_64-linux --no-out-link (or x86_64-darwin on macOS)

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