Skip to content

🐛 Remove the erroneous, trailing space in filename#27520

Merged
kristoferbaxter merged 1 commit intoampproject:masterfrom
zapthedingbat:fix-space-in-filename
Apr 4, 2020
Merged

🐛 Remove the erroneous, trailing space in filename#27520
kristoferbaxter merged 1 commit intoampproject:masterfrom
zapthedingbat:fix-space-in-filename

Conversation

@zapthedingbat
Copy link
Copy Markdown
Contributor

The build-system\babel-plugins\babel-plugin-transform-function-declarations\test\fixtures\transform-assertions\arguments-identifier\options.json had a trailing space in the file name that stopped the repo being cloned on a windows file system. This PR simply removes the space.

@googlebot
Copy link
Copy Markdown

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

@amp-owners-bot
Copy link
Copy Markdown

amp-owners-bot Bot commented Apr 1, 2020

Hey @erwinmombay, these files were changed:

build-system/babel-plugins/babel-plugin-transform-function-declarations/test/fixtures/transform-assertions/arguments-identifier/options.json

@zapthedingbat
Copy link
Copy Markdown
Contributor Author

@googlebot I signed it!

@googlebot
Copy link
Copy Markdown

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: yes and removed cla: no labels Apr 1, 2020
@zapthedingbat zapthedingbat force-pushed the fix-space-in-filename branch from bffae9e to 350e448 Compare April 1, 2020 13:24
@zapthedingbat
Copy link
Copy Markdown
Contributor Author

@kristoferbaxter it looks like this might have happened in a recent refactor.

Copy link
Copy Markdown
Contributor

@mdmower mdmower left a comment

Choose a reason for hiding this comment

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

This looks correct to me:

mdmower@X1 ~/source/amphtml $ ls -l build-system/babel-plugins/babel-plugin-transform-function-declarations/test/fixtures/transform-assertions/arguments-identifier/
total 12
-rw-r--r-- 1 mdmower mdmower 695 Apr  2 11:00  input.js
-rw-r--r-- 1 mdmower mdmower  80 Apr  2 11:00 'options.json '
-rw-r--r-- 1 mdmower mdmower 695 Apr  2 11:00  output.js

Hopefully an OWNER will review and accept soon. I hit a similar issue in amp-toolbox recently: ampproject/amp-toolbox#673

@jridgewell jridgewell closed this Apr 3, 2020
@jridgewell jridgewell reopened this Apr 3, 2020
@jridgewell
Copy link
Copy Markdown
Contributor

I kicked travis to restart.

@kristoferbaxter
Copy link
Copy Markdown
Contributor

Apologies, just saw this.

@rsimha - Can we get a Windows build check added to the environment via Github Actions? This would be a nice additional gate for our development and prevent future issues like this one.

@rsimha
Copy link
Copy Markdown
Contributor

rsimha commented Apr 3, 2020

@rsimha - Can we get a Windows build check added to the environment via Github Actions? This would be a nice additional gate for our development and prevent future issues like this one.

It's something we've talked about, but I'm not sure if we ever got to the point of trying it out. Can you file a FR under ampproject/amphtml and tag @wg-infra?

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 this pull request may close these issues.

6 participants