You can view issues you've commented on by using the following search string in your Issues page search box:
(Replace username with your GitHub username.)
This will show all issues that you've commented on. To show only open issues, add the is:open qualifier.
PRO tag refers to https://github.com/pro
GitHub today (07.01.2019) announced that it is changing the name of the GitHub Developer suite to GitHub Pro. The company says it’s doing so in order to "help developers better identify the tools they need".
In other words, all Pro (and Edu) users have that PRO tag.
Honorable mention: Historically GitHub always ...
Click on the "Insights" tab of the repository that you want to see the oldest commit, followed by the "Network" sub-tab on the left menu bar. When the page is fully loaded (i.e. you can see lots of lines joining and all), press Shift+← to go all the way to the first commit. Click on the dot that represents the first commit and you can get it.
Note! This answer is old and outdated, please check the other answers here, as well as checking the current Terms of Service.
(rest of answer is left as-is)
According to the GitHub Terms of Service, under section G. General Conditions, you'll find this:
You may use GitHub subdomains (e.g., yourname.github.io) solely as permitted and intended by the GitHub ...
I know this is an old question, but I don't see a very detailed answer of the possibilities to strikethrough your text. So here's my answer:
There are several ways to do it:
<strike>strike</strike> → strike
<del>strike</del> → strike
<s>strike</s> → strike
~~strike~~ → ~~strike~~
~strike~ → ~...
It is possible to create a new folder from the web interface, but it would require you to have at least one file within the folder when creating it.
When using the normal way of creating new files through the web interface, you can type in the folder into the file name to create the file within that new directory.
E.g. If I would like to create the file ...
You can view all the issues on Github you have commented on by going to https://github.com/notifications/subscriptions and selecting Reason as Comment.
This will show all the issues that you've commented on.
You can also filter the issues by selecting other reason such as Assign, Author, Manual, Mention, etc. but you can select only one reason at a time. ...
This update came with the "New year, new GitHub" blog post.
It indicates you got the "GitHub Pro" plan. (it used to be called "GitHub Developer" pack)
GitHub Developer is now called GitHub Pro. It includes everything in GitHub Free, unlimited collaborators for private repositories, and advanced code review tools for private and public repositories.
Yes, it is possible to have multiple GitHub Pages sites within one account. Create another GitHub repository and push your site files to the gh-pages branch. This would result in the site being hosted at tshepang.github.io/<repo-name>.
Now, push another file "CNAME" to the same repository and branch and fill it with movies.tshepang.net. Log in to your ...
As mentioned on this thread of the GitHub Google group, repository owners can delete pages from the edit view.
The delete button might be easy to miss, since the buttons from the view mode:
...become only slightly different in edit mode:
Perhaps GitHub should consider making the interface more obvious (e.g. making the delete button red, or something like ...
Officially confirmed to be impossible.
Answer from GitHub support:
Thanks for reaching out to GitHub Support about using GitHub Pages
We set the following Cache-Control header for all GitHub Pages content:
This header is the same for all assets on all sites on our Pages service, and we don't currently provide a way to alter the ...
In response to the answer above:
As of January 30th, 2013, GitHub now allow relative links.
Make sure that you append ?raw=true to the end of the URL, though. Here is an example:
Due to the way GitHub handles URL's, if you do not append ?raw=true to the source URL your browser will attempt to ...
It's gonna be easier.
Go to the Forked Repo (yours) and just click button - "New pull request".
On the page that opens, there is a small link to "switching base" in the message underneath the dropdownselects. Click the link.
Now it will automatically lead to your original repo. Click Create Pull Request button and write some commit message.
Now it ...
So here's a crazy hack. If you create a new github account and make a bunch of gists, you can then convert that account into an Organization and the gists stay associated with the new Organization.
Big caveat: you won't be able to create any new gists for that Organization. But you can edit existing ones. :-\
The server at github.io certainly does caching.
I have a demo up an running over there and was able to determine that the server sets Last-Modified which allows a client to use If-Modified-Since and get 304 from the server if the data has not been modified since it was last fetched. The server also sets CacheControl: max-age=600. I'm not cache specialist ...
GitHub storage limits as of Sep 2015
Per repository git file: 100 MB (strict)
GitHub will warn you when pushing files larger than 50 MB. You will not be allowed to push files larger than 100 MB.
Per repository: ~1 GB (recommended)
We recommend repositories be ...
Go to GitHub settings
You'll see this:
☑ Automatically watch repositoiries
When you’re given push access to a repository, automatically receive notifications for it.
If you uncheck or untick that box you should now have to manually watch repositories that are added by your joined organisation if they've also given you push access.
Git has a separate concept of the author (the person who wrote the code) and committer (the person who committed it to the repository). Similarly there can be different dates for both. They are usually the same.
You'd want them to be different primarily if the person writing the code or submitting the patch does not have push access to the repository as ...
Github uses content-disposition: attachment for PDFs, which downloads the file automatically on github.com. You can host the file on a static page provided by GitHub which can link to this file and update as you update the PDF. For that, you can see github pages.
Create a repo named USERNAME.github.io.
In that repo, click Settings then click ...
I just stumbled across an app called Stargazers forks which lets you see all the forked versions of a repo regardless of how many forks there are. You can sort by number of issues, stars, or last updated.
For example: http://forked.yannick.io/odoo/odoo
If you're viewing the contents of the file itself there should be a "Raw" button.
You can either:
Right-click on that and select the "Save content as..." (or similar depending on your browser)
Click through to see the contents dumped onto the screen and save from there
Actually you can search for issues across repositories by including the author:$author. Here is an example that searches for all issues created by me.
Search for your own issues by putting in your username instead: https://github.com/search?o=desc&q=author:[username]&s=created&type=Issues
Use Google Docs viewer with a url like: