question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"Found .only in folder" error when trying to commit

See original GitHub issue

Current behavior:

I tried to commit into my own branch in my fork of cypress. This fails with the error:

Found .only in folder(s) 👎 544: * Mocks global clock but only overrides specific functions. 1847: * Creates a spy / stub but only for calls with given arguments. 2108: * Whether Cypress will upload the video to the Dashboard even if all tests are passing. This applies only when recording your runs to the Dashboard. Turn this off if you’d like the video uploaded only when there are failing tests. 2721: * Causes all .keys assertions that follow in the chain to only require that the target have at least one of the given keys. This is the opposite of .all, which requires that the target have all of the given keys. 3221: * Causes all .keys assertions that follow in the chain to only require that the target not have at least one of the given keys. This is the opposite of .all, which requires that the target have all of the given keys. 4352: /** Override name for display purposes only */

But I have done nothing related to this I think.

Desired behavior:

I should be able to commit on Windows without using “–no-verify”

Steps to reproduce: (app code and test code)

Fork cypress-io/cypress repo, make a branch and try to commit the changes made in https://github.com/gabbersepp/cypress/commit/de0a7c0d4936886b1b7576b60bb0b533c9207cb2

Versions

Current develop branch, Win10

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
bz2commented, Dec 10, 2020

@jennifer-shehane As (but slightly delayed) promised, brought the change I made on the doc repo over to fix the same issue here.

1reaction
bz2commented, Nov 3, 2019

@jennifer-shehane Yes, this looks very similar to the issue that I proposed a fix for in https://github.com/cypress-io/cypress-documentation/pull/2194 - I can work a similar change in the main repo is the approach is approved.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to fix: error: '<filename>' does not have a commit checked ...
git folder 📁 , it causes the error. So just delete that folder and then try again. It will be working. Save this...
Read more >
File differs from already included file only in casing: correct ...
It happens whenever I change the casing of a directory name and try to commit the change. Git doesn't recognize change in casing...
Read more >
How to Fix "Read-only file system" error when I run something ...
This worked for me: First, run this command with sudo permission: sudo fsck -n -f. Then reboot the machine.
Read more >
TortoiseSVN's Settings
The only condition that keeps the dialog open is an error condition, which occurs when Subversion is unable to complete the task. For...
Read more >
Unable to Delete File: Being Used By Another Person or ...
This error message occurs when the folder or files in the folder are currently used by Windows or another program running.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found