Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed last year.
Improve this question
I am using GitHub for my git repository. Now there are some tasks like "implement feature x" that still have to be done for my app. Is it possible to manage these tasks on GitHub? How? There are issues, but for me issues are problems, bugs, etc. and not tasks - or is my understanding of the term "issue" wrong?
"Issues" is an implementation of what other websites call tickets and sometimes just bugs.
What you use it for is basically up to you to decide. Bugs are an obvious example, but definitely not the only ones. Github provides tags to provide metadata to issues and one common usage of tags is to indicate what kind of "issue" it is.
As an example Angular has a feature tag which they put on issues that are about adding features. Many other project use a similar structure.
Basically: if it will lead to code being merged then it can definitely be an issue and you'll benefit from all the inter-linking within Github. Even if it doesn't result in code (such as topics related to organization of a project) it might be appropriate to put it into Github issues.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Someone copy my github repository and created another github repository simillar to my own. That person changed my name with his codename. And didn't even put a credits.
Is that considered as Plagiarism?
If no, can you explain why?
And if yes, can you tell me what I should do?
It is plagiarism. Which is perfectly legal, unless it leads to fraud (like getting a job based on the brilliant code in a git repository that the person never wrote). In academia it will have massive consequences if found out.
More important, it is copyright infringement. Send a DMCA takedown notice to github, and the repository will disappear very quickly.
In some countries, Germany for example, it violates the right of authorship, which is your right to claim that you wrote the code. In these countries nobody has the right to say they wrote the code when you wrote it, not even your employer - as long as you wrote it. Note this is separate from copyright.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Would using GitHub as a work experience portfolio, including personal projects in various languages/frameworks, be a good practice when seeking employment?
Yes. You'll want to target the specific companies you are applying to, as well. For example, does the company you are targeting value, use, or promote open source projects? Then find some contributions you can make, especially if that company has their own open source projects on GitHub.com.
Definitely host your own projects with a very clear README.md that explains the purpose of the project, anything that showcases design decisions you made, and clear instructions on how to launch/run your project.
No, Since github functions as a site where you host your codes, employers won't have time to access and examine each of your codes.
Yes,
Your future employer may not check out your code, but it will prove that development is your hobby and not only your job.
Put your github repo link in your resume
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
Simply put, can I use github online rather than ever having to download the program for windows. It appears to be much easier than downloading git or the github application. Any thoughts on this?
Yes, you can if you like. Github supports online editing and commit. But I don't think it's convenient since you cannot compile, run and debug your codes, and easy to lost your work when you close your browser without save.
You lose a lot of power by giving up the command line, but you can certainly do most routine tasks in the cloud. You can do some limited editing and repository tasks directly on GitHub, or hook into your GitHub repository with a cloud-based IDE like Cloud9, CodeEnvy, or other similar services.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
What project management solution can you use for grouping together related commits? Lets say you have a few hunderd modules and you need to make changes which affect 5 or 10 of these. Is there a solution that lets you open a ticket and track your subversion commits while keeping a group of people in the loop?
This would depend on the size of your team.
A small team can settle for just using GIT/SVN (or any CVS really) and make sure that everyone pulls/fetches from the integration branch frequently as a habit. If needed, use email to inform everyone about code changes or do scheduled commits to integration branch. This way, instead of letting people know that you did a commit, you can tell people when to expect a commit.
If we are talking about a big team/s, Project Management tools like JIRA should have the flexibility to send an email to a watchlist once a task is done (effectively, a code was pushed) and provide other information about the finished task (such as Affected versions/modules)
Actually, there are different ways to answer your questions depending on the need and workflow of the team but hopefully I've provided some ideas for you here.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I'm writing documentation for a GitHub project and wondering where should I write it to. There seems to be three options: GitHub Pages, GitHub Wiki or a set of Markdown files in the repository (e.g. under docs/ directory) similar to the README.md. Understandably I don't want to write the same documentation to multiple places so I have to pick one.
So what are the differences, pros and cons between the options? Any experience or thoughts about using them especially for project documentation? Also is there other options in addition to the three?
that is a very good question which I personally decide on a change-frequency and number-of-contributors basis.
As an example: in one of our projects (a c++ library) we create a HTML documentation with doxygen once in a while (e.g. while updating the master release branch). That's a perfect match for quasi-static gh-pages. In addition you get a sub domain for it http://<user>.github.io/<project>/ and you can register your own domains on top of it.
An other project contains developer and user documentation (a C++ program). I personally prefer to provide a main workflow for developers in .md files to keep them consistent with the mainline development. Changes will be reviewed by pull requests first.
But for user documentation we choose the build-in wiki since it is very easy to edit and modify - one can even allow modifications by non-members of a team.