I have a problem, I want to get gitkraken pro from the github student pack. I have the little pro tag in Github which means that I have the student pack, but when I connect my github account to Gitkraken it doesn't work, I still have the FREE offer.
Related
I've deployed an app on Netlify through continuous deployment by linking a single Github repo. I had previously been making commits to the project locally, and my contributions were being tracked for this repo. However, now that I've linked the repo to Netlify, it seems no commits or contributions I make are picked up by Github. The commits can still be seen in the Github repo and commits are updated, but the contributions no longer are tracked despite them working previously.
For some context I've checked the Github help page on contributions:
https://help.github.com/en/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile
And cannot see what rule I've violated; I'm working on this on my own, it's a standalone repo, etc etc. considering they were being tracked before for the same repo, I'm confused as to what has changed now that Netlify has been integrated.
Any help/guidance appreciated
So it had nothing to do with Netlify, but my work Mac did not have me globally installed as the commit author with my email. After that, all previous authors were wrong as being my local computer email.
To get around this I followed this tutorial to replace all previous commits with the correct author: How do I change the author and committer name/email for multiple commits?
Would someone please let me know if there is any way to create link to JIRA tickets in my github commit messages?
You can try and follow "Connect Jira Cloud to GitHub", which allows for GitHub or GitHub Enterprise account to be linked to Jira Software.
Your team gets to see their branches, commit messages and pull requests right in the context of the Jira Software issues they're working on
When a developer makes a commit, they should add a Jira Software issue key to the commit message, like this:
git commit -m "PROJ-123 add a README file to the project."
git push origin <branchname>
Update Oct. 2019, you now can set up an autolink reference and GitHub will automatically create links (to external systems) for you.
See "make Jira links clickable in GitHub" (only for GitHub Pro, Team, and Enterprise plans).
We have a few repositories and forks on a trial version of Github Enterprise. I want to evaluate how to migrate from Github enterprise to Github.com (into a paid for organization, say)
The only resource I found was how to perform the migration in the opposite direction
https://help.github.com/enterprise/2.0/admin/articles/moving-a-repository-from-github-com-to-github-enterprise/
I have contacted github.com asking the same questions as below and I am waiting for their response.
How do we migrate a repository from github Enterprise to github.com? (fairly certain that a git clone --bare and a git push --mirror will do the job)
If I migrate forks as well, how do we make sure that the relationship between the original and forks is maintained?
How do I migrate the webhooks and services we configured for our repositories?
How do I transfer the Pull requests/Issues? (article I linked to above says we need to use the Github API, I am OK with this solution)
Can we migrate teams and users? (guessing, probably not)
Note that we have the backups of the enterprise instance performed using the backup tools provided by github (I think it is called ghe-backup)
Thanks
You should be able to use the steps in the linked document in the reverse order as well:
Create an empty repository at github.com
Create a clone of the enterprise repository on your local.
Add github.com as a remote reference on your local clone.
Push all references to the github.com repository.
http://www.alexhadik.com/blog/2016/5/26/migrating-github-repositories-with-gitmover appears to offer a solution: GitMover is "a simple Python script that takes Git repos on any type of GitHub installation, and copies issues, labels and milestones from one to the other. It's the perfect tool to help automate the open-sourcing of an internal project."
This is the story.
I have two computers, one is in my home, another is in my office. Both computers have installed Eclipse and connect to the same project of my github account wtih Egit. I find that when I commit on my home computer, my commit will be recorded and display on my contribution graph. However, when I commit on my office computer, commits will not be recorded.
To solve this problem, I delete projects both on my home computer and office computer, and create new project by cloning corresponding project on github.com with identical steps. Furthermore, I use the same eclipse version, they are the newest Mars. However, the problem still remains, commits on home computer will be recorded, and the other will not.
I searched the Internet and can not find the answer. Is there anybody here can help me out? Thanks in advance!
Problem solved. If someone else meet the similar problem, the following link will be quite useful. https://help.github.com/articles/why-are-my-commits-linked-to-the-wrong-user
Just add your second machines SSH key (assuming you use them) to your account and you should be set. then clone your existing project from the repo, and start working normally. any changes, just commit/push, and from the other machine you can always pull any updates, vice versa.
Commits will appear on your contributions graph if they meet all of the following conditions:
The commits were made within the past year.
The email address used for the commits is associated with your GitHub account.
The commits were made in a standalone repository, not a fork.
The commits were made:
In the repository's default branch (usually master)
In the gh-pages branch (for repositories with Project Pages sites)
In addition, at least one of the following must be true:
You are a collaborator on the repository or are a member of the organization - that owns the repository.
You have forked the repository.
You have opened a pull request or issue in the repository.
You have starred the repository.
Contributions to private repositories will only appear to users who can access those repositories. Those contributions are not rendered for users who cannot access those repositories.
We have a few repositories and forks on a trial version of Github Enterprise. I want to evaluate how to migrate from Github enterprise to Github.com (into a paid for organization, say)
The only resource I found was how to perform the migration in the opposite direction
https://help.github.com/enterprise/2.0/admin/articles/moving-a-repository-from-github-com-to-github-enterprise/
I have contacted github.com asking the same questions as below and I am waiting for their response.
How do we migrate a repository from github Enterprise to github.com? (fairly certain that a git clone --bare and a git push --mirror will do the job)
If I migrate forks as well, how do we make sure that the relationship between the original and forks is maintained?
How do I migrate the webhooks and services we configured for our repositories?
How do I transfer the Pull requests/Issues? (article I linked to above says we need to use the Github API, I am OK with this solution)
Can we migrate teams and users? (guessing, probably not)
Note that we have the backups of the enterprise instance performed using the backup tools provided by github (I think it is called ghe-backup)
Thanks
You should be able to use the steps in the linked document in the reverse order as well:
Create an empty repository at github.com
Create a clone of the enterprise repository on your local.
Add github.com as a remote reference on your local clone.
Push all references to the github.com repository.
http://www.alexhadik.com/blog/2016/5/26/migrating-github-repositories-with-gitmover appears to offer a solution: GitMover is "a simple Python script that takes Git repos on any type of GitHub installation, and copies issues, labels and milestones from one to the other. It's the perfect tool to help automate the open-sourcing of an internal project."