forked from CenterForOpenScience/osf.io
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add gv messaging #208
Draft
Johnetordoff
wants to merge
19
commits into
develop
Choose a base branch
from
add-gv-messaging
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Add gv messaging #208
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
Johnetordoff
force-pushed
the
add-gv-messaging
branch
5 times, most recently
from
March 18, 2024 13:19
bfc4d7d
to
bab4498
Compare
Johnetordoff
force-pushed
the
add-gv-messaging
branch
from
March 18, 2024 13:54
bab4498
to
0c734c7
Compare
Johnetordoff
force-pushed
the
add-gv-messaging
branch
3 times, most recently
from
March 18, 2024 16:49
c2f8d64
to
ccf79c9
Compare
Johnetordoff
force-pushed
the
add-gv-messaging
branch
2 times, most recently
from
March 18, 2024 17:17
5deab16
to
1d70541
Compare
Johnetordoff
force-pushed
the
add-gv-messaging
branch
8 times, most recently
from
March 18, 2024 20:00
155f238
to
238a4d3
Compare
Johnetordoff
force-pushed
the
add-gv-messaging
branch
from
March 18, 2024 20:06
238a4d3
to
378ea48
Compare
Johnetordoff
force-pushed
the
add-gv-messaging
branch
2 times, most recently
from
March 19, 2024 17:31
be3ea64
to
abb17a1
Compare
Johnetordoff
force-pushed
the
add-gv-messaging
branch
from
March 19, 2024 17:57
abb17a1
to
96f153f
Compare
Johnetordoff
force-pushed
the
add-gv-messaging
branch
from
March 19, 2024 21:28
5765f59
to
fb10ff8
Compare
Johnetordoff
force-pushed
the
add-gv-messaging
branch
3 times, most recently
from
March 20, 2024 02:47
927f67c
to
dba4a13
Compare
Johnetordoff
force-pushed
the
add-gv-messaging
branch
from
March 20, 2024 11:12
dba4a13
to
b4a6403
Compare
into add-gv-messaging * 'develop' of https://github.com/CenterForOpenScience/osf.io: add waffling for GV (CenterForOpenScience#10571) Prevent iterable TypeError Exclude self when looking for users to merge [ENG-5356] Unlimit the number of highlighted subjects are displayed (CenterForOpenScience#10569) ENG-5429 fix styling for advisory board section (CenterForOpenScience#10570) Use public schema for function allow request `request_identifier_update` to create DOIs
Johnetordoff
force-pushed
the
add-gv-messaging
branch
from
March 28, 2024 20:45
35edc73
to
dcbc57a
Compare
Johnetordoff
force-pushed
the
add-gv-messaging
branch
from
April 10, 2024 22:22
560c15b
to
92502bf
Compare
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.
Purpose
Changes
QA Notes
Please make verification statements inspired by your code and what your code touches.
What are the areas of risk?
Any concerns/considerations/questions that development raised?
Documentation
Side Effects
Ticket