adding buildings #151
Merged
adding buildings #151
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sammybams
requested changes
Oct 8, 2023
There was a problem hiding this comment.
Thank you very much @Ajlightpro. These contributions are appreciated. But there are some wrongfully classified bungalows which are meant to be storey buildings. Please kindly review and make changes and we would be happy to merge your pull request.
|
All right I’ll make changes
…On Sun, 8 Oct 2023 at 10:23, Samuel Bamgbola ***@***.***> wrote:
***@***.**** requested changes on this pull request.
Thank you very much @Ajlightpro <https://github.com/Ajlightpro>. These
contributions are appreciated. But there are some wrongfully classified
bungalows which are meant to be storey buildings. Please kindly review and
make changes and we would be happy to merge your pull request.
—
Reply to this email directly, view it on GitHub
<#151 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4FQYKAHFTW77WE7SKRZHMDX6JWHNAVCNFSM6AAAAAA5XQ3Q3KVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTMNRTGE4TMNZSGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
dings
|
Alright @Ajlightpro, we'll be expecting. |
|
Could you please add the high rise and story building, so I will know am
left to push the bungalow sir.?
…On Sun, 8 Oct 2023 at 20:27, Samuel Bamgbola ***@***.***> wrote:
Alright @Ajlightpro <https://github.com/Ajlightpro>, we'll be expecting.
—
Reply to this email directly, view it on GitHub
<#151 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4FQYKCUPLIW6CRHDGEYN6LX6L5B5AVCNFSM6AAAAAA5XQ3Q3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGE2DAMZRGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Alright. Don't bother @Ajlightpro. We'll fix the mixup from our end. |
|
Ok, thanks.
…On Sun, 8 Oct 2023 at 21:11, Samuel Bamgbola ***@***.***> wrote:
Alright. Don't bother @Ajlightpro <https://github.com/Ajlightpro>. We'll
fix the mixup from our end.
—
Reply to this email directly, view it on GitHub
<#151 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4FQYKDIHWHI54RL7XTHIOLX6MCIXAVCNFSM6AAAAAA5XQ3Q3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGE2TCMJWGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sammybams
approved these changes
Oct 8, 2023
There was a problem hiding this comment.
Thank you @Ajlightpro. The mix up will be sorted from our end. You don't need to change anything.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
dings