Skip to content

Instantly share code, notes, and snippets.

View mbehr1's full-sized avatar

Matthias Behr mbehr1

  • Germany, Munich
View GitHub Profile
@tfc
tfc / short_file.cpp
Created February 20, 2016 20:14
__SHORT_FILE__ Macro
#include <stdio.h>
using cstr = const char * const;
static cstr constexpr past_last_slash(cstr str, cstr last_slash)
{
return
*str == '\0' ? last_slash :
*str == '/' ? past_last_slash(str + 1, str + 1)
: past_last_slash(str + 1, last_slash);
}
@Chaser324
Chaser324 / GitHub-Forking.md
Last active July 15, 2024 22:34
GitHub Standard Fork & Pull Request Workflow

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j