Hot answers tagged github
131
I would argue that "in the age of GitHub, Stack Exchange, Coursera, Udacity, blogs, etc." the relevance of a concise and a well written resume is more important than ever.
As an employer, I am not going to start with your github projects and blog posts. I might end up checking them if:
your resume is relevant to my job requirements;
and your resume ...
115
Look at a resume as a distilled brochure that advertises highlights from your skills and experience. A combination of your github and SO profiles and a bunch of other online resources may be complete and accurate, but it isn't sorted or otherwise prepared for easy reading in any way. People who hire want you to tell them what you think distinguishes you from ...
71
I think this question is just a special case of "Why should I learn any CLI for which a GUI alternative exist?". I suspect the latter question is about as old as GUIs, and I assume there were many attempts to answer it over the years.
I could try to bumble my way through my own answer to this question, but Neal Stephenson articulated what I agree with as ...
42
Are your images original work or can they be recovered (guaranteed?) from else where? Are they needed to ship a software unit built from source?
If they are original, they need backing up. Put them in you rev control, if the never change, the space penalty is the same as a backup, and they are where you need them.
Can they be edited to change the ...
38
You are technically correct -- no real need to push if you aren't sharing the code with anyone.
Then again, your laptop has a hard drive made by the lowest bidder. Your house could burn down before the hard drive fails. You might want to look at your code remotely. Or even share it with someone.
Now, with Github, they require everything be public or you ...
38
Membership in an OSS project is not the same as a funded, corporate team where people are interviewed and chosen. The source is already out there (it isn't open source otherwise). Tell them to send in some patches. If they are good patches (and you must review them first), commit them. Once the prospect builds up trust and a a history of making valuable ...
34
I'd be insanely leery about putting my company's intellectual property on someone else's servers, no matter who it is.
Is GitHub Enterprise out of the question for your company? AFAIK, it deals with all of these types of potential security risks out of the box.
31
Most of the CLI-only features only come into play when you accidentally get your repository into a weird state and want to fix it. On the other hand, the most common way to get your repo into a weird state is to use advanced features you don't understand. If you stick to what the GUI provides, that will cover your needs 99% of the time.
The other reason ...
28
Of course it is OK: it is hard to imagine that over 4,098,118 projects currently hosted on GitHub would all be 100% great and useful! You are not forcing anyone to use your code or even to look at it. If you host the project primarily for yourself, the quality of your code is of concern to you, and nobody else.
You listed all the right reasons to host your ...
23
I once heard a résumé described as "a balance sheet that shows only your assets but not your liabilities".
Based on this definition, you want to include projects that will be an asset to you in getting the job while leaving out those that might be a liability. This means they should be relevant to the job you are applying for and show off your best work. ...
22
Markdown is a simple syntax for providing semantic info and representing common formatting in plain text. Daring Fireball has a awesome syntax guide for standard markdown. GitHub then uses a variant of this that they call GitHub Flavored Markdown.
To set up your readme just create a plain text file and name it README (or README.md / README.markdown) and ...
22
Most HR screening these days done by recruiters and corporate HR departments is automated resume reading. A human never sees your resume/application. A computer program that searches out keywords in a plain text, HTML or Word document determines if your resume matches the specified job criteria.
If it's a match, a HR person, who knows nothing about GitHub ...
21
I've used GitHub profiles, twitter streams, and blogs all as indicators of quality in programming interviews/candidate screening. They all generate different signals in their own way.
9 out of 10 applicants have never submitted a single patch to a single open source project. Even updating broken documentation puts you into an upper echelon of developer. It ...
21
I use tag classes like this:
For the issue type I have:
type:bug
type:feature
type:invalid
For issue priorities I use:
prio:low
prio:normal
prio:high
And for an issue's states I use:
status:confirmed
status:deferred
status:fix-committed
status:in-progress
status:incomplete
status:rejected
status:resolved
For additionaly informational tags I ...
21
If there was a benefit, it would merely be painful. But nothing sucks worse than painful and pointless. Just have the single personal account. Two reasons:
Github has incredibly good access control in their organizations. If an employee leaves, you can instantly remove their access. If they had a company account, you'd have to reclaim the account somehow ...
21
I'm I missing something here?
Yes. Relying on people not knowing your source code to prevent them from finding security exploits in it is known as security through obscurity.
The problem: it doesn't work. Skilled hackers don't need the source code to find and exploit vulnerabilities. They'll do some fuzzing to find input that causes problems and then ...
18
Also, are there any particular practices that I need to start doing in anticipation of adding others to my projects in the future?
Of course. There is a simple good practice that you can use even if you don't have a team right now: create a separated branch for development. The idea is that master branch will contain only released code versions or major ...
17
Small: massive - a single file dynamic database wrapper by Rob Conery
Medium: RestSharp - a REST client by John Sheehan
Larger: RavenDB - a document database by Ayende Rahien
17
The movie superstars, who command multi-million-dollar flat fees to appear in movies, still have resumes with a headshot and recent achievements, which they send to directors/producers when they're interested in a role.
Thus, the first and foremost function of a resume. It tells me you're interested enough in the job to do the work of compiling or tailoring ...
15
Why the hell not? :)
Storing binaries is considered bad practice, yes, but I never worried too much about images.
Worst case, if you have tons, store them somewhere else or use externals or an extension for binary support. And if the images won't be changed that often, then where's the problem? You won't get a big fat delta. And if they get removed over ...
15
I work in a team which uses git, where 40+ developers are working on multiple code repositories(100+) at any given point of time. We also started out with very few developers, growing the team size in a span of few years. In the beginning though with few people you can get away with knowing only a bare minimum of git. Over time you will improve your git fu, ...
14
The advantages git has come from tossing out a lot of old assumptions about what a VCS should do. The disadvantages git has come from not being able to leverage prior experience and not being able to do things the way you are used to.
If you are going to switch from something else to git, try to start tabula-rasa (though it is impossible to truly do in ...
14
The GitHub issue tracker is quite flexible. There is indeed no priority, nor ordering. It revolves around three major pillars: Assignment, labels and milestones.
You can "tag" issues with labels you create (in a similar way than Gmail labels). For instance: "bug", "feature-request", "todo", "question", ... One issue can be tagged with different labels.
You ...
13
There's a few things I might be concerned with, as a disinterested third party. So let me toss some questions at you that you'd better be prepared to answer (to your IT department):
Any version control is better than none. We have plenty to choose from, what's wrong with those?
Distributed version control? What's that? How do we control that?
What does ...
13
When it comes to git, I believe one should commit as often as possible - some people commit every successful compilation. Don't confuse commits with pushes - a local commit does not have to be pushed (and with git, you should use many branches as they are cheap).
This should be the rule all around, but some SCMs are too slow for such a rule.
Personally, ...
13
Make the fork, then make a branch immediately.
Now you have an "untouched" master that can be updated itself going forward to get the latest changes with git pulls.
Keep you branch local without pushing to remote and you can do rebases which will do the following for you:
save away your changes
apply the latest changes from master to your branch (the ...
12
Is your company's code in public or private repositories? If they (or at least some) are public, and you allowed your employees to use their own GitHub accounts, then it would be an incentive for them to write good code. Their name would literally be attached to it, publicly. However, I'll assume that all of your repositories are private.
Overall, it sounds ...
12
Not out of the question, and actually a pretty good idea.
Regrettable as it may be, you need to plan on your employees leaving the organization at some point in the company's life. How are you going to extricate their personal accounts from the company's repository at that point in time?
What are you going to do if the employee leaves on bad terms? In an ...
12
CLAs generally exist to do several things:
They keep you revoking your code down the road. In countries that are signatory t to the Bern convention, authors exclusively retain copyright on all original works, with others allowed to copy it only with explicit permission. A CLA makes you give that permission explicitly—and frequently in perpetuity, ...
10
If you have a private server with ssh access all you need to do is this:
ssh my.server
mkdir ~/repo.git && cd ~/repo.git
git init --bare # bare repository that will serve as backup location
exit
# back on your box
cd $my_local_git_repo
git remote add --mirror backup ssh://my_server:repo.git
git config remote.backup.fetch ":" # don't replace our data ...
Only top voted, non community-wiki answers of a minimum length are eligible
