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

JAM_ADM0 Update #2837

Merged
merged 1 commit into from
May 2, 2023
Merged

JAM_ADM0 Update #2837

merged 1 commit into from
May 2, 2023

Conversation

11helenab
Copy link
Collaborator

Why do we need this boundary?

Anything Unusual?

@11helenab
Copy link
Collaborator Author

Issue #2758

@github-actions
Copy link

Hello! I am the geoBoundary Bot, and I just did an initial check on your submitted files.

I will automatically re-run my checks when you edit your Pull Request, and provide the new results in a comment just like this.
Once all of your files meet my programmed standards, I will flag your file for a manual human review.
=========== Submission Findings ===========

Full logs for fileChecks

Full logs for geometryDataChecks

Full logs for metaChecks

All checks have passed! I'll flag your boundary submission for a manual review by one of my humans.
Preview

Copy link
Collaborator

@amanda-reed amanda-reed left a comment

Choose a reason for hiding this comment

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

Looks great-thank you! closes #2758

@DanRunfola DanRunfola merged commit bd5b361 into main May 2, 2023
4 checks passed
@DanRunfola DanRunfola deleted the JAM_ADM0 branch May 2, 2023 15:15
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.

None yet

3 participants