# GitHub | ![img \|150](https://upload.wikimedia.org/wikipedia/commons/thumb/c/c2/GitHub_Invertocat_Logo.svg/320px-GitHub_Invertocat_Logo.svg.png) | **GitHub**, Inc. is a platform and cloud-based service for software development and version control using Git, allowing developers to store and manage their code. It provides the distributed version control of Git plus access control, bug tracking, software feature requests, task management, continuous integration, and wikis for every project. Headquartered in California, it has been a subsidiary of Microsoft since 2018. | |-|-| | | wikipedia:: [GitHub](https://en.wikipedia.org/wiki/GitHub) | url:: [GitHub](https://github.com/) - Contributions - https://help.github.com/articles/viewing-contributions-on-your-profile/ - https://help.github.com/en/articles/why-are-my-contributions-not-showing-up-on-my-profile - Issues - https://help.github.com/en/articles/assigning-issues-and-pull-requests-to-other-github-users - https://help.github.com/en/articles/permission-levels-for-a-user-account-repository - Collaborator - https://help.github.com/en/articles/closing-issues-using-keywords - You can't assign issues to anyone unless you have write access to that repo, or if the repo is owned by an organization instead of a person, you can grant more granular permissions like read, write, etc. to the repo. but not sure if you can assign issues with only read access. - Starting a new Repo - I think its easier to initialize locally and then push to a new repo on GitHub that has been created without the initialize with readme checkbox checked. - And instead of cloning from the remote, you can skip cloning and just add the remote url and then pull. - [[Software License]] - [[Markdown]] is widely supported in comments, etc. also animated gifs, emoji, file attachments (drag and drop) etc. for commit messages, etc. - Reviews - https://help.github.com/en/articles/reviewing-proposed-changes-in-a-pull-request - https://help.github.com/en/articles/about-pull-request-reviews - Code Owners - https://help.github.com/en/articles/about-code-owners - [[GitHub Pages]] - GitHub Desktop - https://desktop.github.com/ - Searching - Tip: You can find a pull request where you or a team you're a member of is requested for review with the search qualifier review-requested:\[USERNAME\] or team-review-requested:\[TEAMNAME\]. For more information, see "Searching issues and pull requests." - Forking - Label issues and pull requests - Pull Request - a GitHub thing - By incorporating certain keywords into the text of your Pull Request, you can associate issues with code. When your Pull Request is merged, the related issues are also closed. For example, entering the phrase Closes \#32 would close issue number 32 in the repository. - Releases and tags - [Managing releases in a repository - GitHub Docs](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository) - Learning - https://guides.github.com/activities/hello-world/ - https://github.com/explore - https://guides.github.com/introduction/flow/ - https://services.github.com/on-demand/ - https://guides.github.com/ ## [[GitHub Actions]] ## [[GitHub DependaBot]] ## [[GItHub CLI gh]]