Switch from .dev to .test #923
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
swalkinshaw
approved these changes
Nov 18, 2017
retlehs
added a commit
to roots/sage
that referenced
this pull request
Nov 19, 2017
oxyc
added a commit
to generoi/sage
that referenced
this pull request
Jan 8, 2018
* upstream/master: Don't need this any more! :( This moves our eslint config in .eslint.js, which allows us to use conditionals in the config file itself, significantly simpliying rule creation. For small-scale differences, this seems to be the simplest solution. Rename production eslint file from `.eslintrcProd` to `.eslint.production.json` as per suggestion from @swalkinshaw: roots#2008 (comment) Build process now allows console.log, except when the `production` flag is set on `yarn build`, in which case it will throw an error. Delete .eslintrc Remove some Bower traces Update README.md Add Code of Conduct [ci skip] Change .dev to .test for default local dev TLD per roots/trellis#923 Bootstrap function in _variables.scss to play nice with other frameworks Move variables and Bootstrap imports to autoload Remove explicit Bootstrap lines Example $theme-color Update main.scss Update controller examples Update dependencies Update CHANGELOG [ci skip] Bootstrap 4 Beta 2 Remove get_the_posts_navigation from 404
ptrckvzn
added a commit
to ptrckvzn/sage
that referenced
this pull request
Jan 30, 2018
* sage/master: Updated bootstrap to release version 4.0.0 Updated popper.js to version 1.12.9 Add php-mbstring to list of requirements Don't need this any more! :( This moves our eslint config in .eslint.js, which allows us to use conditionals in the config file itself, significantly simpliying rule creation. For small-scale differences, this seems to be the simplest solution. Rename production eslint file from `.eslintrcProd` to `.eslint.production.json` as per suggestion from @swalkinshaw: roots#2008 (comment) Build process now allows console.log, except when the `production` flag is set on `yarn build`, in which case it will throw an error. Delete .eslintrc Remove some Bower traces Update README.md Add Code of Conduct [ci skip] Change .dev to .test for default local dev TLD per roots/trellis#923 Bootstrap function in _variables.scss to play nice with other frameworks Move variables and Bootstrap imports to autoload Remove explicit Bootstrap lines Example $theme-color Update main.scss Update controller examples
ashleyrevlett
added a commit
to relaydesignco/sage
that referenced
this pull request
Feb 14, 2018
* master: (339 commits) Update CHANGELOG.md 9.0.0 Update README [ci skip] Update CHANGELOG [ci skip] npm lockfile Update dependencies Updated bootstrap to release version 4.0.0 Updated popper.js to version 1.12.9 Add php-mbstring to list of requirements Don't need this any more! :( This moves our eslint config in .eslint.js, which allows us to use conditionals in the config file itself, significantly simpliying rule creation. For small-scale differences, this seems to be the simplest solution. Rename production eslint file from `.eslintrcProd` to `.eslint.production.json` as per suggestion from @swalkinshaw: roots#2008 (comment) Build process now allows console.log, except when the `production` flag is set on `yarn build`, in which case it will throw an error. Delete .eslintrc Remove some Bower traces Update README.md Add Code of Conduct [ci skip] Change .dev to .test for default local dev TLD per roots/trellis#923 Bootstrap function in _variables.scss to play nice with other frameworks Move variables and Bootstrap imports to autoload Remove explicit Bootstrap lines ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
see #580 and https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/
also: https://roots.io/guides/updating-development-tld-from-dev-to-test/