mesa@piefed.social to Programming@programming.devEnglish · 7 hours agoCopilot is now injecting ads into GitHub pull requests. It's a disaster.www.windowscentral.comexternal-linkmessage-square34fedilinkarrow-up1232 cross-posted to: technology@lemmy.world
arrow-up1232external-linkCopilot is now injecting ads into GitHub pull requests. It's a disaster.www.windowscentral.commesa@piefed.social to Programming@programming.devEnglish · 7 hours agomessage-square34fedilink cross-posted to: technology@lemmy.world
minus-squaremesa@piefed.socialOPlinkfedilinkEnglisharrow-up1·3 hours agoHow did you get the CI working in codeberg? last time I checked, you had to get permission to do so(?). I would love to switch when I have time.
minus-squareuuj8za@piefed.sociallinkfedilinkEnglisharrow-up2·edit-23 hours agoYou do have to ask for permission. https://docs.codeberg.org/ci/ Asking permission involves creating an issue on the Codeberg-e.V./requests repo: https://codeberg.org/Codeberg-e.V./requests/issues/new?template=ISSUE_TEMPLATE%2FWoodpecker-CI.yaml Here’s an example issue asking permission for CI: https://codeberg.org/Codeberg-e.V./requests/issues/1663 They get back to you fairly quickly. I think the main thing they check for is if your project is FOSS. They don’t seem very strict otherwise. After you get permission, you can go to https://ci.codeberg.org/login to access CI. You’ll also need to create a .woodpecker folder in your repo. Woodpecker docs are here: https://woodpecker-ci.org/docs/usage/intro # .woodpecker/my-first-workflow.yaml when: - event: push branch: main steps: - name: build image: debian commands: - echo "This is the build step" - echo "binary-data-123" > executable - name: a-test-step image: golang:1.16 commands: - echo "Testing ..." - ./executable
How did you get the CI working in codeberg? last time I checked, you had to get permission to do so(?). I would love to switch when I have time.
You do have to ask for permission. https://docs.codeberg.org/ci/
Asking permission involves creating an issue on the
Codeberg-e.V./requestsrepo: https://codeberg.org/Codeberg-e.V./requests/issues/new?template=ISSUE_TEMPLATE%2FWoodpecker-CI.yamlHere’s an example issue asking permission for CI: https://codeberg.org/Codeberg-e.V./requests/issues/1663
They get back to you fairly quickly. I think the main thing they check for is if your project is FOSS. They don’t seem very strict otherwise.
After you get permission, you can go to https://ci.codeberg.org/login to access CI.
You’ll also need to create a
.woodpeckerfolder in your repo.Woodpecker docs are here: https://woodpecker-ci.org/docs/usage/intro
# .woodpecker/my-first-workflow.yaml when: - event: push branch: main steps: - name: build image: debian commands: - echo "This is the build step" - echo "binary-data-123" > executable - name: a-test-step image: golang:1.16 commands: - echo "Testing ..." - ./executable