We are migrating the issues of a project from Google Code to GitHub. Google's migration tool assigns all the issues in GitHub to the user GoogleCodeExporter. How can I change issue's author in GitHub?
The GitHub API has a function to edit issues that will allow you to change the assignee (not creator) of the issue. As far as I know, there is no functionality within GitHub to change the creator.
I'm sorry that this doesn't accomplish exactly what you want to do, but it might be the closest alternative (depending on what your project uses issue creator for).
Related
I have it in my head to help people at my company get better by finding a way to highlight and call out good code.
In particular, I'd like to be able to mark a file (not a repository or directory) as having a "gold star" (or another badge) so people browsing our source code who see the badge can see they're looking at a really good implementation they might take inspiration from.
I'm taking inspiration from the code owners feature on GitHub where there's a little padlock icon on a file if it's assigned ownership by the CODEOWNERS file.
Is it possible to do a custom "badge" on GitHub? If so, what's the API?
Browsing the GitHub documentation and searching online, I wasn't able to find anything explaining how to do something like this. Most folks were talking about the little images badges like the code coverage badges people put in their readme files.
Checkout this thread. You can submit feature request to GitLab and GitHub or in case of GitLab code your own feature and submit PR.
Here are some closely related discussions. Probably you have already seen them and are not looking for them but you might use them to get idea of how to create the feature that you want.
The Shields service (at shields.io) provides a way to create custom badges for your projects. These are badges are very common and are frequently used to show status information about the project, or demonstrate tools that were used for the development of your project. (...more)
Also checkout Bring Your Own Badge
Is the code for the actual GitHub website/application hosted on GitHub?
Yes, GitHub is developed on GitHub, using a variety of repositories. Most of the code is private, but some tools are open source and in public repositories. This is not in any way a secret, and multiple talks have been given about the way GitHub builds GitHub and the way the company uses it, which is relatively nontraditional.
This allows employees to test new features in their everyday work to make sure that they're functional and of excellent quality before release, and to think of new useful functionality to add.
I have heard that, product based companies will look for what we have done outside of projects and also looking for the github profile.
In the meantime, I have created an automation application which addresses the specific requirement (Timesheet) in our organization. So, I thought of uploading this one too.
I have also done the screen cast and uploaded it to YouTube for adding in the profile (Resume).
This exact tool is not useful for all the people , but useful for the people in our organization, in which they can edit/contribute more.
Now I am having the question like, can I upload this kind of the code to GitHub?
Thanks.
Yes, you can.
Code on GitHub does not have to be useful to other people. You can push code there even if it is only useful to you or people in your organization.
You could also use a private repository if you do not want other people to see the code.
See: https://github.com/pricing
I want to open the issues tab when I open repository because I made a repository just for collecting the tasks for all my project , How can we do that ?
As #VonC has said, this is NOT configurable. It seems that what you require is an issue tracker and not specifically a repository. This articles may help you find an issue tracker that fits your purpose:
http://mashable.com/2014/02/16/bug-tracking-apps/
http://www.thegeekstuff.com/2010/08/bug-tracking-system/
Github's feature for referencing issues in commits automatically just by using the # and referencing commits in issues using the commit hash id is powerful. But is it a maintainable or scalable approach to handle issues from different repositories in one central repository? I do not think so. Issues are important in project development and should be kept organised the same way we keep code clean and organised.
However, this does not mean that it is not possible to maintain your issues in a single github repository. Instead of trying to have the issues tab open automatically, you may create a manual, as a README, for instructions on utilizing the reported issues. This manual will be shown to users visiting the repo. See https://github.com/keybase/keybase-issues as an example. You may find this github article useful in referencing issues.
This doesn't seem to be configurable.
That means you need to open your repo directly at the "Issues" page:
https://github.com/<username>/<reponame>/issues
GitHub seems to be creating releases out of tags whenever I push those tags up to a GitHub repository that I've cloned to my own machine. How do I prevent GitHub from doing this? If I wanted a release, I'd go into GitHub and create one from a pre-existing tag, but I don't want all of my tags to be associated with releases!
I didn't find anything related to disabling this behavior in GitHub's help pages, so I think that it may not be possible to disable this. The best you can do is ask their support team to see if this feature exists or, if that doesn't work, ask for it — the support team's members are awesome and will pay attention to you for sure.