• 1 Post
  • 22 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle

  • Asked several to write a c implementation of some basic networking stuff.

    ChatGPT: needed to refine my input, got reasonable output. Complete answers, just compile and run.

    Google: the output was just a few snippets, nothing to be used as-is.

    MSFT: terrible output, and -no suprise here- the compiled code crashed with null pointer references etc. The worst answers ever.

    For simple problems (programming low-level microcontrollers), my go to will be ChatGPT everytime.

    Google should get it’s act together, Microsoft can exit the stage.











  • Still testing and fiddling, but I’m using the forgejo-runner. Renovate is just another repository, with a workflow to get it started:

    on:
      schedule:
        - cron: '5 2 * * *'
        - cron: '5 14 * * *'
    
    jobs:
      build:
        runs-on: docker
        container:
          image: renovate/renovate:37.140-full
        steps:
          - name: Checkout
            uses: actions/checkout@v3
    
          - name: Run renovate
            env:
              PAT: ${{ secrets.PAT }}
              GITHUB_COM_TOKEN: ${{ secrets.GITHUB }}
            run: |
              echo "Running renovate"
              cd ${GITHUB_WORKSPACE}
              renovate --token ${PAT}          
    

    The renovate image has been pulled by hand and the forgejo-runner will happily start the image. Both PAT and GITHUB secrets are configured as ‘action secrets’ within the renovate repository.

    Besides the workflow, the repository contains renovate.json and config.js, so renovate has the correct configuration.




  • I totally agree, but this depends. It helps if you have backups already in place, if a few additional containers or VM’s won’t matter much etc.

    Running forgejo and runners took me way less effort than properly setting up sendmail for instance.

    It all depends on skills, resources etc. Everyone needs to make these decisions themselves.