removing broken link for writing expressions #227
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wegank
reviewed
Jan 5, 2024
|
Please also squash the commits, thanks. |
henrik-ch
force-pushed
the
broken-expression-link
branch
from
60bd19b
to
79fc2bb
Compare
henrik-ch
force-pushed
the
broken-expression-link
branch
from
79fc2bb
to
8f45311
Compare
(second attempt)
wegank
approved these changes
Jan 6, 2024
|
🤯 I had some trouble with the rebase and blew up my branch, but have hopefully recreated it correctly now. @wegank sorry for this and thanks for your patience. |
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2024-01-11-documentation-team-meeting-notes-103/38124/1 |
Could we just squash on merge? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replacing with nix.dev language basics link.
(not a 100% substitute)
Trying to address #226 but of course open for other suggestions as well.