remove gradle #38
remove gradle #38
Conversation
There was a problem hiding this comment.
Would be nice to land this into master and then rebase #29 on it since most of the changes are unrelated to #29 and im not sure when #29 will land.
Would you be able to change the PR base to master and just remove my work in progress page additions? I can worry about rebasing #29 onto master after that.
|
On second thought I'll make the changes to remove my work in-progress page. Should be minimal change, then we can change the PR base to master. |
flyinprogrammer
changed the base branch from
feature/getting-started-docs
to
master
flyinprogrammer
changed the base branch from
master
to
feature/getting-started-docs
flyinprogrammer
changed the base branch from
feature/getting-started-docs
to
master
flatten directories move content into content- folders update documentation based on changes
flyinprogrammer
force-pushed
the
feature/no-mo-gradle
branch
from
a8af9ac
to
8882039
Compare
use https for css.link
fix URL to be DEPLOY_URL
missed moving svgs in rebase
|
This is now ready for review again. I believe when it lands in |
add minimum netlify.toml
| TODO: @flyinprogrammer needs to fix this because it's all garbage once we start using Netlify. | ||
| Starting with the fact that PROJECT_BASE_URL will likely become DEPLOY_URL from Netlify, but | ||
| what will that value be for contributors or people who want to fork ¯\_(ツ)_/¯ |
There was a problem hiding this comment.
Is this TODO now complete that we have netlify setup or still an open item?
There was a problem hiding this comment.
not really i was waiting for things to roll on to master so i could then use the fork->PR process to fix it 😂
flatten directories
move content into content- folders
update documentation based on changes