-
Notifications
You must be signed in to change notification settings - Fork 90
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: laamaa/m8c
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.7.6
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: laamaa/m8c
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.7.7
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 10 commits
- 8 files changed
- 4 contributors
Commits on Jul 8, 2024
-
Update version and hash in default.nix to 1.7.6
GitHub Actions committedJul 8, 2024 Configuration menu - View commit details
-
Copy full SHA for b956da8 - Browse repository at this point
Copy the full SHA b956da8View commit details
Commits on Jul 26, 2024
-
Flakes are a different way to specify a Nix project/configuration. It provides a few benefits over the existing solution: 1. The exact versions of inputs are snapshot. This should mean that a build on one machine will use the exact same packages as the build on another. 2. Flakes can be consumed by other Flakes. This would mean that folks could use this Flake as an import and then declaritively configure their `m8c` setup. 3. While not used here now, this could make versioning easier. There wouldn't need to be a `fetchFromGitHub` step because someone could just use/run the app for that tagged branch. Ex: `nix run github:laamaa/m8c?ref=v1.7.7` That said, this PR does rely on flake-compat to provide backward compatibility with `default.nix` and `shell.nix`. So a user could use `nix-shell` as before, or they could use `nix develop` (and potentially devenv in the future).
Configuration menu - View commit details
-
Copy full SHA for 6d94013 - Browse repository at this point
Copy the full SHA 6d94013View commit details
Commits on Aug 7, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 9e6cbaf - Browse repository at this point
Copy the full SHA 9e6cbafView commit details
Commits on Aug 8, 2024
-
Configuration menu - View commit details
-
Copy full SHA for d731a8f - Browse repository at this point
Copy the full SHA d731a8fView commit details
Commits on Aug 14, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 1b79d40 - Browse repository at this point
Copy the full SHA 1b79d40View commit details
Commits on Aug 15, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 08a8809 - Browse repository at this point
Copy the full SHA 08a8809View commit details -
Configuration menu - View commit details
-
Copy full SHA for bd3496f - Browse repository at this point
Copy the full SHA bd3496fView commit details
Commits on Aug 16, 2024
-
Configuration menu - View commit details
-
Copy full SHA for fa45b7d - Browse repository at this point
Copy the full SHA fa45b7dView commit details -
Configuration menu - View commit details
-
Copy full SHA for cfe1295 - Browse repository at this point
Copy the full SHA cfe1295View commit details -
Configuration menu - View commit details
-
Copy full SHA for aa9f3cd - Browse repository at this point
Copy the full SHA aa9f3cdView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.7.6...v1.7.7