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

feat: Add Mid and East Antrim Council #428

Closed
wants to merge 12 commits into from
Closed

feat: Add Mid and East Antrim Council #428

wants to merge 12 commits into from

Conversation

PhilDB-cloud
Copy link
Contributor

@PhilDB-cloud PhilDB-cloud commented Nov 15, 2023

feat: Add integration for Mid and East Antrim Borough Council. I have tested it stand alone and I have run the poetry test script for it and it passes. Happy for you to make any suggestions and I can follow up or for you to make edits directly. The website is not particularly easy to scrape. Doesn't use postcode or uprn so ends up with multiple matches for most addresses searched.

initial commit for mid and east antrim bin collection data
update extraction of date from html
first cut following offline test
Add Mid and East Antrim
remove paon line as only use postcode but it needs to contain the address
@dp247
Copy link
Collaborator

dp247 commented Nov 21, 2023

feat: Add integration for Mid and East Antrim Borough Council. I have tested it stand alone and I have run the poetry test script for it and it passes. Happy for you to make any suggestions and I can follow up or for you to make edits directly. The website is not particularly easy to scrape. Doesn't use postcode or uprn so ends up with multiple matches for most addresses searched.

Could you push an extra commit with the 'feat:' in, please? Otherwise happy to merge 😁

@PhilDB-cloud PhilDB-cloud changed the title Mid and East Antrim Council feat: Add Mid and East Antrim Council Nov 21, 2023
@PhilDB-cloud
Copy link
Contributor Author

@dp247 Thanks for reviewing. I have attempted to commit with 'feat:' in. Please let me know if I need to do it differently. I'm not very well versed in colaborating in git.

@robbrad
Copy link
Owner

robbrad commented Nov 22, 2023

@OliverCullimore : Does the full commit history need every commit message to have the conventional commit prefix?

@robbrad
Copy link
Owner

robbrad commented Nov 22, 2023

@PhilDB-cloud in the mean time while Oliver looks into the previous commit history being effected by the pipeline can you try

git rebase -i HEAD~25

Be careful to only edit the commit history of your commit - just add feat: before each and I think you should be good

Dont change the pick or the other messages

@OliverCullimore
Copy link
Collaborator

@robbrad for neatness of the release changelog and for the lint action to pass every commit in the PR is supposed to have a prefix.

But as long as one commit has a correct prefix the automated releases will work so you can ignore the lint action and merge if you like.

@PhilDB-cloud
Copy link
Contributor Author

thanks all. I should have some time tonight to look at rebasing it.

@PhilDB-cloud
Copy link
Contributor Author

I was thinking I would just close this pull request and delete the branch and then start again. It seems less risky and won't take me long to do. Does that sound ok?

@dp247
Copy link
Collaborator

dp247 commented Nov 23, 2023

Entirely your call, I'm more than happy to merge this as is

@PhilDB-cloud
Copy link
Contributor Author

It seems like it will keep things neater so happy enough to do it.

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.

4 participants