Closed
Conversation
…nction that creates xml based off the updated json, merged Will's javascript changes, consolidated functions related to motherdb to the motherpype.py file (there still may be more to do),
# Conflicts: # webapp/home/metapype_client.py # webapp/views/donor/do.py # webapp/views/donor/forms.py # webapp/views/donor/templates/donor.html
…w strings relating to stain types and source information did not appear to have any equivalents.
… populate_ihc_form respectively wherever possible. Added import statements in both for mdb_names as with motherpype.py.
…om Scratch"/"other_entity" page, had to remove the need for a node_id value in the url which may cause issues depending on how important said value actually is
Steven dev
Made award number a required field and changed to form label from opt…
…k metadata page. Closes #99
Steven dev
Steven dev
When other is selected it disables the stage of cycle field. Still need to make it Convert to a text box when other is selected. Added unspecified to life stage.
Steven dev
Help Button For Check Metadata Page
… as option as it was incomplete
Collaborator
|
Hi @gaferna, I see that you have initiated a PR to our primary ezEML repository with 343 commits affecting 204 files. Was this PR intentional (to merge into our upstream branch)? Or were you trying to limit the PR to your project's locally forked repository? Thanks, |
Author
|
Hello,
The PR was accidental, i was trying to pushing to mother development branch
and github had set the push defaulted to the primary ezEML repository when
I trying to push to the development branch for the mother repository.
…On Thu, Jul 6, 2023 at 1:46 PM Mark Servilla ***@***.***> wrote:
Hi @gaferna <https://github.com/gaferna>,
I see that you have initiated a PR to our primary ezEML repository with
343 commits affecting 204 files. Was this PR intentional (to merge into our
upstream branch)? Or were you trying to limit the PR to your project's
locally forked repository?
Thanks,
Mark
—
Reply to this email directly, view it on GitHub
<#110 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A75ZKSWJXR5JKIBCO47WW3TXO4PYRANCNFSM6AAAAAAZ47WBNI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Collaborator
|
No worries @gaferna, I will close this PR. |
Author
|
thank you. I thought I had closed it when I realized it was a mistake
…On Thu, Jul 6, 2023 at 2:09 PM Mark Servilla ***@***.***> wrote:
Closed #110 <#110>.
—
Reply to this email directly, view it on GitHub
<#110 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A75ZKSQUQHP2O76TZY5DNPLXO4SPXANCNFSM6AAAAAAZ47WBNI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
No description provided.