• Activity
  • Votes
  • Comments
  • New
  • All activity
  • Showing only topics in ~tech with the tag "github". Back to normal view / Search all groups
    1. Is there a sane way to use Git as a glorified sync tool?

      I am not a programmer nor am I in IT, but I like to use some of the same tools they use. I use Emacs for writing fiction and I like it a lot. One of the packages I use with Emacs is...

      I am not a programmer nor am I in IT, but I like to use some of the same tools they use. I use Emacs for writing fiction and I like it a lot. One of the packages I use with Emacs is git-timemachine, which allows me to visualize all the previously commited versions of the file I am currently working on. It serves as a very good and very reliable undo system. All my writing is on a private repo on Github. My usage is so simple and basic, Git/Github only serves as a kind of backup and undo (I know Git is not a backup, so I regularly download my repos as zips and send to OneDrive as an extra. They are also always available offline in the machines work, of course).

      The problem is, sometimes I work on different machines, and sometimes on different operating systems on the same machine (via dual boot). So I would like to know if there's an easy way to always "sync" the local mirror I am currently working on with the latest changes (also making sure that all changes are pushed). Essentially, I am asking if I can make Git work like Dropbox or OneDrive by automatically accept changes as long as they are the most recent version of a file. I do not wish to go through diffs approving every single change.

      I understand I could use something like rclone for that, but their bisync feature is still very new and not considered reliable. Also, I already use Git and it is good for me. So I would prefer not adding an extra piece to the puzzle.

      I am familiar with cron, have an elementary understanding of shell scripts, and can follow instructions.

      So, can Git do the job?

      28 votes
    2. To use Disqus or Giscus (Github Discussions) for comments is the conundrum

      I happen to host my blog https://prahladyeri.github.io/blog statically, built using Pelican and served on Github Pages. Plebs like us can't afford a backend server infrastructure, so we must rely...

      I happen to host my blog https://prahladyeri.github.io/blog statically, built using Pelican and served on Github Pages. Plebs like us can't afford a backend server infrastructure, so we must rely on external services like Disqus for comment hosting.

      So far, Disqus was the only fellow in town who allowed us to host comments on a free plan. Though there were some issues (bloat, adware, etc.), people seemed to be generally happy with it so far.

      But now, a new fellow named giscus commenting system has entered the town, it's basically powered by github. Since I already host my blog on github pages, this should be a natural choice for me, right? Many bloggers seem to be migrating to this new system and I might too soon. The downsides however are as follows:

      1. It won't allow me to export existing comments from the old disqus system. Understandable to an extent as those exact author usernames may not be on the Github platform?
      2. Disqus interface seems to have improved all of a sudden in last few days! There no longer seem to be any ad and even the comment interface seems to be less heavy or cluttered now. It might sound a bit conspiratorial in nature but could this be the result of rising competition in the form of Giscus!

      I'm a lazy status-quoist by nature and might well end up retaining disqus if they don't deviate too much from where they are now. But I'll keep an eye out on Giscus too and its progress. What do you guys suggest?

      5 votes
    3. Looking for a GitHub CLI tool

      And no, I'm not talking about git. I'm looking for a tool that I can use in scripts to automate non-git tasks on GitHub such as creating new repositories, drafting releases, uploading assets to a...

      And no, I'm not talking about git. I'm looking for a tool that I can use in scripts to automate non-git tasks on GitHub such as creating new repositories, drafting releases, uploading assets to a release, etc.

      I started dipping my toes into gh, GitHub's official cli tool, but when I created a repository it immediately cloned it, which is not what I want. I know I can just rm -rf the repo but ideally the tool I use would do only what I tell it and nothing more.

      Reading the docs for hub, it might do what I want, although I have some reservations about the project after reading this post written by the developer: https://mislav.net/2020/01/github-cli/

      I've also come across git-hub, which doesn't support creating repos AFAICT, and git-spindle, which doesn't support uploading assets.

      Are there any other command line GitHub clients I should consider?

      Which one do you use? What's your experience with it been like?

      5 votes