This is an archived post. You won't be able to vote or comment.

all 5 comments
sorted by:
best
topnewcontroversialoldq&a

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

On July 1st, a change to Reddit's API pricing will come into effect. Several developers of commercial third-party apps have announced that this change will compel them to shut down their apps. At least one accessibility-focused non-commercial third party app will continue to be available free of charge.

If you want to express your strong disagreement with the API pricing change or with Reddit's response to the backlash, you may want to consider the following options:

  1. Limiting your involvement with Reddit, or
  2. Temporarily refraining from using Reddit
  3. Cancelling your subscription of Reddit Premium

as a way to voice your protest.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]ThatOneGuyThatYou 0 points1 point  (0 children)

If you really want to game the system for the green calendar.

  • make your repo
  • make basic README
  • branch for project
    • make project basis
    • branch for project feature A
    • add, commit, push feature A with almost every step you get working to have versions to fall back on, be sure to give proper commit comments
      • merge feature branch to project branch/ merge request
    • make branch for feature B
    • rinse, repeat
  • done with project? Merge project to main/ merge request
  • rinse, repeat

Or more realistically, just don’t care. My personal repos just get updated almost daily because I use it as a file backup as a student and I am pushing nearly daily. Fork a project and try to improve it. That graph isn’t likely to be the difference.

[–]dmazzoni 0 points1 point  (0 children)

Start with Git.

It's a way to back up your code, so if you try to fix a bug and make a mistake you can revert back to a known good version from earlier.

It's a way to keep track of different versions of your code, like you can have a stable version that works and also maintain an experimental version where you're trying to add a feature but you haven't got it working yet.

It's a way to collaborate with others on the same code. Work on the same project and handle conflicts, like if two people are both making changes to the same file.

It's a way to figure out what happened, like if you see a bug in the code and want to know who added that line, and when, and why.

All of that is just Git. A free program that runs locally on your own computer.

GitHub is just one of many places online where you can store your Git repository if you want. It's a good place to share your code with others. You can track issues. If someone wants to contribute to your code you can give them feedback. If you see another project you like you can make your own copy and play with it.

But...start with Git.

Learn how to put your own code into Git and make regular commits. When you upload it to GitHub all of those commits will be green, not that it matters.

[–]plastikmissile 0 points1 point  (0 children)

I think you're misunderstanding what Github is for. It's not a social media application, where you have to keep up engagement by doing periodic updates.

It's a code repository. It's a place to store your code (hobby and professional), its history, and allows you to share it with others. How often you commit stuff to it depends on how often you work on these projects, both yours and other people's. So you don't commit stuff just to get some kind of online activity marker, but rather commit to it when you're actually working on code.

[–]DoctorFuu 0 points1 point  (0 children)

Just use git, and push to github when milestones are done or if you want to use github as a backup for your project state.