Skip to content

Conversation

@plaindocs
Copy link
Collaborator

I did look at Dependabot, but I don't think it quite works for this scenario.

@netlify
Copy link

netlify bot commented Aug 26, 2025

Deploy Preview for scrc-coding-guidelines ready!

Name Link
🔨 Latest commit ad73d97
🔍 Latest deploy log https://app.netlify.com/projects/scrc-coding-guidelines/deploys/69272cab536bc80008b9a775
😎 Deploy Preview https://deploy-preview-191--scrc-coding-guidelines.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@felix91gr
Copy link
Collaborator

Given #195 has been merged, maybe it's a good idea to revert the second commit?

@PLeVasseur
Copy link
Collaborator

Hey @plaindocs, following up here to see if you'd be able to look into the feedback.

@felix91gr
Copy link
Collaborator

@plaindocs I'm really looking forward to this! ^^

I just ran again into the need to update the FLS because it was blocking #180 and #181 today :')

@plaindocs
Copy link
Collaborator Author

I'm going to make time to look at this again, soz for the delay.

@plaindocs
Copy link
Collaborator Author

@felix91gr @PLeVasseur ok, I've got a stupid bash script which lets us decide whether to update automatically. Should be easy to connect that to GHA input/output to make the PR conditional on that. But I ran out of time today before heading off for two weeks.

Happy for someone to pick it up and finish it, or I can look when I'm back.

dest = root / "build"

args = ["-b", builder, "-d", dest / "doctrees"]
args = ["-b", builder, "-d", dest / "doctrees", "-wtest.txt"]
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs moving out into a flagged parameter so it doesn't happen with every build.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Under what circumstances does it need to be included?

Copy link
Collaborator Author

@plaindocs plaindocs Dec 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm using that text file to parse out whether we can open the PR to update the build or not, so it's only really needed for this job.

But there isn't a trivially built in way to pass something into that custom build script. I could probably do something with the job name 🤔

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs moving out into a flagged parameter so it doesn't happen with every build.

What would be the consequence if it happened on every build? @plaindocs

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To summarize what we discussed earlier:

  • @plaindocs will update builder/build_cli.py to expose the required parameter
  • Use the exposed parameter and run builder/build_cli.py where appropriate

Did I get that right @plaindocs, @felix91gr?

@plaindocs
Copy link
Collaborator Author

I've not looked into the Python version build error.

@plaindocs
Copy link
Collaborator Author

plaindocs commented Nov 26, 2025

OK this maybe sorta works at this point. Hard to test, although I suppose I could manually revert the FLS code, so it has to update it.

@felix91gr any idea on how to easily move this parameter out so it's not happening on every run?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Automation] Update the FLS spec lock_file whenever it's trivial to do

3 participants