-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Rename extension directories main .md files to README.md #1648
Conversation
I hacked together a bash script for this. #!/usr/bin/env bash
echo "changing to "$1
cd $1
for i in $(find . -maxdepth 2 -name "*.md")
do
b=$(basename $i)
base=${b%.*}
dir=$(dirname $i)
parent_dir_name_regex="[\/]+"$base"$"
if [[ $dir =~ $parent_dir_name_regex ]]; then
echo "git mv"
echo $i
echo "$dir/README.md"
git mv $i $dir/README.md
fi
done I manually checked the renaming but if you notice something wrong with the script, that may translate to incorrect renaming. |
Doing a grep search (
Looks like you'll also need to rebase off of the the upstream master. |
ac00c50
to
08715cf
Compare
@jridgewell, I made the replacements and rebased onto master. I used a slightly different regex ( |
Fancy. 😉 Still seeing one more in |
Scary PR. Thanks for doing this! Are @Meggin @pbakaus and @erwinmombay on board with this for the docs-site? |
Ah, nice catch. That must have slipped in after the rebase and I didn't rerun the search. |
08715cf
to
e681603
Compare
Replacement made, rebased on master, and squashed. @jridgewell, ready for another check. Hopefully I got everything this time. 😄 |
Looks like the continuous-integration check is failing. The failure is coming from |
@pbakaus and @erwinmombay are the best people to check this error. Important realization this morning-- not only will the build script need updating on the /docs side of things, but all the cross-references to the files throughout the docs will be broken, and this isn't good. We need to coordinate the changes to the filenames and the /docs script and the links at the same time so that the site isn't super-broken. Just to re-iterate, if we merge just the README changes, the current links in the site will be broken. And that's not good. |
Brian-- once we hear back from Erwin or Paul on how to fix the gulp error, I can sync with you to make sure we get the /docs links ready for README changes. We just need to coordinate together. |
Meggin-- This may be handled with how I modified the I have it set up to take in the However, if there are any full references in the docs site to an extension |
For convenience, here is the issue for handling the renaming in the docs repo: ampproject/amp.dev#20. |
Nice, Brian. Once we here back about gulp error, let's coordinate our Basically once the READMEs go live, I need to run the script right away, The longer this doesn't happen, the longer we've got broken links. Meggin On Fri, Jan 29, 2016 at 10:44 AM, Brian Tice [email protected]
|
Meggin-- Sounds good. I'm not familiar with the release strategies for amp but I'll do my best to make sure you're in the loop before this gets merged into master. I guess @jridgewell just needs to be aware of the coordination requirement. |
the validator error is caused by https://github.com/ampproject/amphtml/blob/master/validator/validator_test.js#L142 we'll probably need to fix this internally. i can make the changes. /cc @powdercloud |
This LGTM, deferring to @erwinmombay to merge when the docs site can be updated. |
For convenience, here is the PR for changes on the docs side: ampproject/amp.dev#26. |
hey all, so i'm wondering if we should leave the The other option is of course wait until the validator goes live and then merge this. (somebody will have to pay attention to when the server code goes live and then merge this) let me know. |
+1 to leaving files until both PRs are merged. Simple way to keep stuff On Fri, Jan 29, 2016 at 3:33 PM, erwin mombay [email protected]
|
For the validator: I think we need to point the links to ampproject.org anyways. I'd rather do that than some refactoring still pointing at the github pages. I hope that the ampproject.org links will be stable and that pages that move will be configured with 301s, etc. Perhaps at some point some of these reference docs can be translated. Best of all: they're AMP Pages!!! :-) |
I filed #1687 to document the intent to fixup the validator spec links. |
@Meggin are you ok with the proposed change? |
Can somebody resolve the conflicts and give me a quick overview of what this PR is trying to achieve? I've recently made some fixes to the importer that are of similar nature (I wrote the original importer). |
I think this one is obsolete, so I'm closing it. Please feel free to reopen or comment if you disagree. Thanks much! |
Addresses #1304.