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

[internal] Rename generate-lockfiles to gen-lockfiles #12680

Closed
wants to merge 1 commit into from

Conversation

Eric-Arellano
Copy link
Contributor

See #12641 for why we're using this naming scheme of generate-lockfiles instead of something more succinct like lock. tl;dr: the semantics for lockfiles will improve in Pants 2.8+, e.g. autogenerating the lockfile when necessary, and we don't want to commit to a highly generic name till that is all worked out.

Still, @benjyw pointed out in #12676 that gen-lockfiles is more concise than generate-lockfiles and probably does not lose much clarity. We already use the "gen" abbrevation, like export-codegen. Note that gen-lockfiles is still a verb, which we want for goal names.

[ci skip-rust]
[ci skip-build-wheels]

# Rust tests and lints will be skipped. Delete if not intended.
[ci skip-rust]

# Building wheels and fs_util will be skipped. Delete if not intended.
[ci skip-build-wheels]
Copy link
Member

@kaos kaos left a comment

Choose a reason for hiding this comment

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

Makes sense.

@stuhood
Copy link
Member

stuhood commented Aug 27, 2021

IMO, let's just leave these with the obviously temporary names until the semantics are settled in #12591. As described there, if we're going for cargo semantics, the final name will be something like update, and so minor tweaks for length aren't really worth it.

@Eric-Arellano
Copy link
Contributor Author

Sure, that's fine with me. Ideally you aren't running these goals much either, unlike fmt and test

@Eric-Arellano Eric-Arellano deleted the gen-lockfiles branch March 15, 2022 20:51
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.

3 participants