• 1 Post
  • 30 Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle



  • Eager Eagle@lemmy.worldtolinuxmemes@lemmy.world•Rule
    link
    fedilink
    English
    arrow-up
    6
    ·
    2 months ago

    it’s safer to run it as a regular user and have topgrade ask for root access. With this config line it can ask ahead when starting, so you don’t need to babysit it:

    [misc]
        # ...
        # Run `sudo -v` to cache credentials at the start of the run; this avoids a
        # blocking password prompt in the middle of a possibly-unattended run.
        pre_sudo = true
    



  • Unpopular opinion, but most of that is duplicated information that makes sense to be duplicated because I’m not a machine that can scan the whole page and instantly get what I need.

    Top right are action buttons, fork and stars on the center right let you see who else starred and forked the repo.

    License information just makes sense to be in a repo summary, and it just happens that most license files are at the root and visible in the file tree.

    I don’t see the top level stuff, you probably see that because you’re not authenticated, so github tries to “sell” itself for you.

    I agree “releases” should be at the top though (it used to, and I use GitHub refined to bring it back), but having the latest one at a glance is nice and saved me a click many times.








  • As someone who said it before, I was recommending that to technical people having technical problems because of the stupid way windows does some things.

    So while I can’t speak for anyone saying that, it doesn’t mean it’ll always work, or even that you’ll have less problems, but it does usually mean that it’s easier to figure out what’s wrong and how to fix it because the system is so open.