[github-actions]

Automated changes by create-pull-request GitHub action

[netlify]

✅ Deploy Preview for pyos-website ready!

Name	Link
🔨 Latest commit	d13525c
🔍 Latest deploy log	https://app.netlify.com/projects/pyos-website/deploys/6ac6daa1030e0700070289cc
😎 Deploy Preview	https://deploy-preview-964--pyos-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[InessaPawson]

@lwasser Same pattern as #962.

I think the easiest fix is on the pyosmeta side: tell ruamel not to wrap by setting yaml.width = 4096 in export_yaml.

[lwasser]

@lwasser Same pattern as #962.

I think the easiest fix is on the pyosmeta side: tell ruamel not to wrap by setting yaml.width = 4096 in export_yaml.

Ok so what's happening if i understand correctly is that our workflow is adding trailing white space to each line and then precommit removes it so it's empty as a pr?

i see that now and it's happening in our contributors workflow too specific to the bios . that seems like a good fix so bios are just a single line. and we can then cut a new release of pyosmeta. should we open an issue over in pyosmeta and link it to this pr? then maybe see if anyone wants to tackle it?

[lwasser]

alternatively and additionally we could turn off the editorial workflow running on a cron since we don't onboard editors that often and the contrib workflow runs on sundays and runs this workflow too.

[InessaPawson]

@lwasser I'd do both. Let me know if you need any help.

[lwasser]

ok @InessaPawson, I implemented this here: #968 to remove the cron step. Feel free to review/merge if you're happy, or ask for changes.

I don't have bandwidth right now to fix the YAML width issue, but might tomorrow. Or we can open an issue and see if someone in Slack has bandwidth (since you are doing so much here!!). Just let me know what you think, and I will support that approach!

[lwasser]

Let me check Slack to see if someone has bandwidth! and if no one bites, then i am happy to try to fix or if you have space but again you are doing a lot already!!

[lwasser]

Ok i created this issue: pyOpenSci/pyosMeta#411
maybe we can promote it in slack to see if anyone has bandwidth to tackle it?? and feel free to add any detail to the issue that you see!!

[InessaPawson]

Closing as the diff is empty.
The weekly cron for this workflow was removed in #968 (manual dispatch verified), so these empty PRs won't keep appearing. The underlying line-wrapping issue is tracked in pyOpenSci/pyosMeta#411.