Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Luton has moved to Luci #34

Merged
merged 18 commits into from
Mar 12, 2023
Merged

Luton has moved to Luci #34

merged 18 commits into from
Mar 12, 2023

Conversation

cpwood
Copy link
Contributor

@cpwood cpwood commented Mar 12, 2023

Changes made accordingly and tests pass. Sutton also still working after a few tweaks to the Luci code.

Coventry still broken - their catalogue has been down for several weeks with a promise of being back online by the beginning of March. It's still not back!

I've noticed that my commits keep showing up again and again in each PR, by the way. Is that because you're squashing them during the PR..?

@DaveBathnes DaveBathnes merged commit 751bc67 into LibrariesHacked:main Mar 12, 2023
@DaveBathnes
Copy link
Member

Hi Chris

Thanks! And yes, I always tend to set policies in GitHub to do squash commits whenever merging to main. I just find that leads to a cleaner main but that's only really the case when people are committing often on feature branches and there's a policy of a single branch per feature.

I've done normal merge this time as the history looks useful! So I'll probably just continue to do that and only squash merge on single-feature branches

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.

2 participants