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

Documentation for stamping is incorrect #156

Closed
mmorearty opened this issue Mar 14, 2018 · 1 comment · Fixed by #162
Closed

Documentation for stamping is incorrect #156

mmorearty opened this issue Mar 14, 2018 · 1 comment · Fixed by #162
Labels

Comments

@mmorearty
Copy link
Contributor

In the readme, the explanation of how to do stamping is wrong. Basically, if you are writing a genrule that has stamp = True, that genrule will only work as expected if it has at least one file in its srcs. See bazelbuild/bazel#4842 for a full explanation.

@alexeagle
Copy link
Collaborator

Ooh, thanks for finding that Mike. Silently stamping with an old value is a nasty bug!

@alexeagle alexeagle added the bug label Mar 19, 2018
alexeagle added a commit to alexeagle/rules_nodejs that referenced this issue Mar 23, 2018
alexeagle added a commit to alexeagle/rules_nodejs that referenced this issue Mar 23, 2018
alexeagle added a commit to alexeagle/rules_nodejs that referenced this issue Mar 23, 2018
alexeagle added a commit to alexeagle/angular that referenced this issue Mar 23, 2018
As pointed out in bazel-contrib/rules_nodejs#156 our mechanism would never pick up changes to the version info.
alexeagle added a commit to alexeagle/angular that referenced this issue Mar 23, 2018
As pointed out in bazel-contrib/rules_nodejs#156
our mechanism would never pick up changes to the version info.
alexeagle added a commit to alexeagle/angular that referenced this issue Mar 28, 2018
As pointed out in bazel-contrib/rules_nodejs#156
our mechanism would never pick up changes to the version info.
alxhub pushed a commit to angular/angular that referenced this issue Mar 28, 2018
As pointed out in bazel-contrib/rules_nodejs#156
our mechanism would never pick up changes to the version info.

PR Close #22965
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants