repo VS logrus

{ "name": "Some name", "version": "1.0.0", "description": "Some description", "repository": { "type": "git", "url": "git+ssh://[email protected]/user/repo" }, "keywords": [ "some", "keywords" ], "author": "you, of course :)", "license": "MIT I hope", "bugs": { "url": "https://github.com/user/repo/issues" }, "homepage": "https://github.com/user/repo#readme" }

pip3 install repolist repolist -u https://github.com/user/repo

# Fork the Repogit clone https://github.com/user/repo.git# Make changes...# Push to the repositorygit push origin master

An HTTPS URL like https://github.com/user/repo.git

# Git Command examples $ git init $ git clone https://github.com/user/repo.git $ git add README.md $ git commit -m "Update README" $ git push origin master

_, err: = git.plainclone ("/tmp/myrepo", false y git.cloneOptions { URL: "https://github.com/user/repo", })

if your repo is https://github.com/user/repo, then run this command

I use https://github.com/user/repo/find/master and it works perfectly, and I only know the structure of a file name, not the actual file name. And this is on a larger repo, 8GB, 14k files, 1500 folders.

git clone https://github.com/user/repo.git # to clone a repository git clone https://github.com/user/repo.git another-repo-name # to clone a repository and give it a different local name

git clone: This command creates a local copy of a remote repository. For example, git clone https://github.com/user/repo.git will create a local copy of the repository located at https://github.com/user/repo.git.

It's some sort of logging system well explained by Alex Edwards in Let’s Go Further. As stated, we could have used logrus or any other popular logging system in Go.

Option 2, please. You may not have been around for the logrus debacle, but it was a giant pain.

For the example I’m using the very popular logrus library and then I’m setting the log formatter to be JSON

For choosing the candidates for the poll, I didn't do any thorough research. I was looking for a library to use in my project at work, and I ended up at sirupsen/logrus which was already being used by one of the dependencies in that project.

I contribute to OSS as part of my job on the regular. The company is good about contributing upstream, signing CLAs, and all that. We still work against private forks for two main reasons: 1. Some changes that we need are not accepted by maintainers based on philosophical or architectural reasons that we can’t otherwise work around. You’re beholden to then unless you publicly fork the repo which has other legal/PR overhead for the company and OSS political implications. 2. Maintainers in the past have taken down repos, renamed repos, or changed the licensing on repos that have left us in a lurch. We always build against our own private forks because we need predictability and can’t be beholden to some other party for business continuity. We sync them down from the public upstream at our leisure.

If they change the case on their username on the other hand, the Go ecosystem explodes: https://github.com/sirupsen/logrus/issues/570#issuecomment-3...

Like, for example, some projects importing logrus with a capital L and some with a lowercase L, and go modules having no way to reconcile the two: https://github.com/sirupsen/logrus/issues/553

Ugh. Wish people would stop using logrus. It’s in maintenance mode and slow, especially its stack tracing.