Skip to content

Conversation

@jcass11
Copy link
Collaborator

@jcass11 jcass11 commented May 1, 2025

No description provided.

Copy link
Contributor

@cfrick13 cfrick13 left a comment

Choose a reason for hiding this comment

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

wondering if we should use the DOI link to the article (https://doi.org/10.1016/j.cels.2025.101265)?

Copy link
Contributor

Choose a reason for hiding this comment

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

should we use the DOI link instead in case the actual link address changes?
https://doi.org/10.1016/j.cels.2025.101265

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Sure! Changing now.

Copy link
Contributor

@cfrick13 cfrick13 left a comment

Choose a reason for hiding this comment

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

Hooray!

Copy link
Collaborator

@chantelleleveille chantelleleveille left a comment

Choose a reason for hiding this comment

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

Fantastic!

@jcass11 jcass11 added this pull request to the merge queue May 5, 2025
Merged via the queue into dev with commit 38fd27a May 5, 2025
1 check passed
@jcass11 jcass11 deleted the update_link branch May 5, 2025 16:20
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