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

[SUGGESTION] Make *.yml optional in initial .yarnclean #4281

Closed
hron84 opened this issue Aug 29, 2017 · 5 comments · Fixed by #4724
Closed

[SUGGESTION] Make *.yml optional in initial .yarnclean #4281

hron84 opened this issue Aug 29, 2017 · 5 comments · Fixed by #4724

Comments

@hron84
Copy link

hron84 commented Aug 29, 2017

Do you want to request a feature or report a bug?

It's just a suggestion

What is the current behavior?
The automagically created .yarnclean includes *.yml which can cause problems on packages like electron-builder that stores messages or other stuffs in YAML (see electron-userland/electron-builder#1487)

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
Make *.yml commented out but still included in newly created .yarnclean files.

Please mention your node.js, yarn and operating system version.
N/A

@BYK
Copy link
Member

BYK commented Sep 27, 2017

I'm +1 for this. @arcanis?

@arcanis
Copy link
Member

arcanis commented Sep 27, 2017

Agree. I'd even be in favor to replace it with an explicit .travis.yml entry.

@BYK
Copy link
Member

BYK commented Sep 27, 2017

@hron would you like to submit a PR? It should be easy ;)

@hron84
Copy link
Author

hron84 commented Sep 29, 2017

@BYK sorry, I'm not too familiar with NodeJS development, I use yarn to handle frontend stuffs. Even worse, I'm not too skilled in JS. I'm really sorry guys, I'd like to help, but I can't. I've no idea where you do these things and I can't figure it out from the source tree at first view.

@sreeramjayan
Copy link

sreeramjayan commented Oct 13, 2017

@BYK @arcanis
Is the requirement to comment out .*.yml and *.yml in yarnclean?

lzhang added a commit to lzhang/yarn that referenced this issue Oct 17, 2017
Address yarnpkg#4281 by removing entries to clean `*.yml` and `.*.yml` from the
default filter list in `.yarnclean`.
@BYK BYK closed this as completed in #4724 Oct 17, 2017
BYK pushed a commit that referenced this issue Oct 17, 2017
…4724)

**Summary**

Remove entries to clean `*.yml` and `.*.yml` from the default filter list in `.yarnclean`. Instead, include configuration files from common CI and build tools.

- Travis CI
- CircleCI
- AppVeyor
- Codeship
- Wercker

Fixes #4281, fixes #2276.

**Test plan**

```shell
$ yarn autoclean --init
yarn autoclean v1.2.1
[1/1] Creating ".yarnclean"...
info Created ".yarnclean". Please review the contents of this file then run "yarn autoclean --force" to perform a clean.
✨  Done in 0.15s.
$ grep yml .yarnclean 
appveyor.yml
circle.yml
codeship-services.yml
codeship-steps.yml
wercker.yml
.travis.yml
```
joaolucasl pushed a commit to joaolucasl/yarn that referenced this issue Oct 27, 2017
…arnpkg#4724)

**Summary**

Remove entries to clean `*.yml` and `.*.yml` from the default filter list in `.yarnclean`. Instead, include configuration files from common CI and build tools.

- Travis CI
- CircleCI
- AppVeyor
- Codeship
- Wercker

Fixes yarnpkg#4281, fixes yarnpkg#2276.

**Test plan**

```shell
$ yarn autoclean --init
yarn autoclean v1.2.1
[1/1] Creating ".yarnclean"...
info Created ".yarnclean". Please review the contents of this file then run "yarn autoclean --force" to perform a clean.
✨  Done in 0.15s.
$ grep yml .yarnclean 
appveyor.yml
circle.yml
codeship-services.yml
codeship-steps.yml
wercker.yml
.travis.yml
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants