Skip to content

contrib: add a wrapper to be able to check deploys use up-to-date git#198

Open
lf- wants to merge 1 commit intozhaofengli:mainfrom
lf-:jade/contrib-footgun-script
Open

contrib: add a wrapper to be able to check deploys use up-to-date git#198
lf- wants to merge 1 commit intozhaofengli:mainfrom
lf-:jade/contrib-footgun-script

Conversation

@lf-
Copy link
Copy Markdown

@lf- lf- commented Mar 4, 2024

This is adapted from an internal project. It's a simple solution that probably has wider applicability than just our little project. I put it in contrib/ to make it clear it is a script that might be useful but isn't like, part of the software.

Usage: copy to your repo, put (pkgs.callPackage ./somewhere/colmena-wrapper {}) in place of colmena in your dev shell.

This is adapted from an internal project. It's a simple solution that
probably has wider applicability than just our little project.
echo >&2
echo "Attempting to deploy when @upstream_branch@ has $only_in_main commits not in your branch!" >&2
echo "This will probably revert someone's changes. Consider merging them." >&2
echo "If you really mean it, set the environment variable FOOTGUN_ME_UWU" >&2
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

FOOTGUN_ME_UWU 🥺

@spinus
Copy link
Copy Markdown

spinus commented Jan 17, 2025

I think adding just few lines with different license than original project license makes it more problematic than it helps.
When people validate licenses for project usage, they are checking repo/project level, nobody is checking if there is one file somewhere with something else.

@lf-
Copy link
Copy Markdown
Author

lf- commented Jan 18, 2025

I think adding just few lines with different license than original project license makes it more problematic than it helps. When people validate licenses for project usage, they are checking repo/project level, nobody is checking if there is one file somewhere with something else.

This is marked as CC0, as in, you can use it for literally any purpose and destroy the license comment on it for all it matters. It is under the project license because it's public domain.

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.

4 participants