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

Migrate to Nix flakes #31

Merged
merged 1 commit into from
Oct 22, 2024
Merged

Migrate to Nix flakes #31

merged 1 commit into from
Oct 22, 2024

Conversation

lloeki
Copy link
Member

@lloeki lloeki commented Oct 22, 2024

Why?

Consistency with other repos

What does this PR do?

Add a Nix flake

How to test the change?

nix flake show
nix develop

Additional Notes:

@lloeki lloeki requested a review from a team as a code owner October 22, 2024 11:37
@@ -1,34 +1,50 @@
name: Nix
name: Test Nix

Choose a reason for hiding this comment

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

🟠 Code Vulnerability

No explicit permissions set for at the workflow level (...read more)

Datadog’s GitHub organization defines default permissions for the GITHUB_TOKEN to be restricted (contents:read, metadata:read, and packages:read).

Your repository may require a different setup, so consider defining permissions for each job following the least privilege principle to restrict the impact of a possible compromise.

You can find the list of all possible permissions in Workflow syntax for GitHub Actions - GitHub Docs. They can be defined at the job or the workflow level.

View in Datadog  Leave us feedback  Documentation

@lloeki lloeki force-pushed the lloeki/migrate-to-nix-flake branch from c418b54 to 5dc3bb2 Compare October 22, 2024 11:40
@lloeki lloeki merged commit 55952c2 into main Oct 22, 2024
20 checks passed
@lloeki lloeki deleted the lloeki/migrate-to-nix-flake branch October 22, 2024 13:49
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