Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

chooglen / git Public

forked from git/git

Notifications You must be signed in to change notification settings
Fork 1
Star 4

Code
Pull requests
Actions
Projects
Security
Insights

Additional navigation options

Code
Pull requests
Actions
Projects
Security
Insights

WIP what breaks if we always die() on config errors? #353

Sign in to view logs

Sign in to view logs

WIP what breaks if we always die() on config errors?

WIP what breaks if we always die() on config errors? #353

Summary
Jobs
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

3 errors

failed: t5750.9 parse config format edge cases: empty key or value

failed: t7450.43 fsck detects corrupt .gitmodules

Process completed with exit code 1.

The logs for this run have expired and are no longer available.

Loading

Re-running jobs...

You can’t perform that action at this time.