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

Task/fp 1378 consistent space above footer #480

Merged
merged 10 commits into from
May 4, 2022
8 changes: 4 additions & 4 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
"npm": "8.5.5"
},
"devDependencies": {
"@tacc/core-styles": "git+https://[email protected]/TACC/Core-Styles.git",
"@tacc/core-styles": "git+https://[email protected]/TACC/Core-Styles.git#task/FP-1378-consistent-space-above-footer",
Copy link
Member Author

@wesleyboar wesleyboar May 3, 2022

Choose a reason for hiding this comment

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

This change is not intended to be merged. After PR approval, I plan to revert this change (and rebuild package-lock.json) so the latest Core-Styles is loaded.

That branch is transient (deleted after merge of the related PR), so merging this change to main would soon result in npm install fail. What I should do, is pin to a specific version… but I am currently loading latest of Core-Styles, to facilitate rapid development. Core-Styles is versioned (releases), but I don't really have a process for Core-Styles, yet. How do I version what hasn't been merged?

"minimist": "^1.2.6",
"node-cmd": "^5.0.0"
},
Expand Down