Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
Can someone help me? I have no idea what to do. If someone could please help me with a step by step process. I have no idea what or if I need to instal something. The only think I know is that I usually lose all my projects so I need a proper way to save them. Btw my knowledge about github is 0
First and foremost, I would learn how to use Git and Github. You can try going here:
https://guides.github.com/
This covers GitHub very well. Considering you are working with Unity, you will want to know what files to put on a repository and what not to expose to the world. The tutorials regarding using a .gitignore file will cover that concept. There really isn't much else you need to know.
As an aside, I would also suggest you check out
Unity Hub . This lets you upload, track and run analysis on your projects from one location.
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 needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I know this is probably a super silly question, but how do I install on my pc open source programs that I find here on github.
By installing I mean directly from the source code, and not by going on some external website and downloading the file from there.
I know I'm a noob, just go easy on me please
Github page of the program will generally show README file, and it would contain instructions on how to install this program. Sometimes you can find the instructions in wiki pages for this project.
There is no one general way to install something from github, it really depends on the software you are looking at.
Quite often, especially if it is a big project and is written in low level language, the main installation step is entering commands
./configure
make
make install
in your terminal, but this is only one of the different installation procedures.
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 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 3 years ago.
Improve this question
I was studying SCM/Bug tracker integration when I found that it is not only possible to close and modify issues from the commit log, but it is also possible to create them.
But since the commit log is for code changes, I don't see why anyone would modify the code to create an issue. Please cite one scenario where this is justifiable.
One scenario might be where you're committing the fix for a particular issue, but you know the issue you've resolved is a short term fix for the problem.
In this case it might be necessary to open another issue in light of the short term fix so that you know you need to provide a long term fix somewhere down the road.
Maybe in a situation where a bug-report includes several "sub-bugs" : the commit can solve one of those "sub-bugs", and create another report for the remaining "sub-bugs" ?
Or sometimes, if you commit some hacky patch to quickly solve an urgent bug, you might want to create another report to "correct the hacky patch", to create a long-term solution ?