cutting duplicated parts from welcome session#1934
Merged
Conversation
❌ DANGER ❌This pull request has modified workflows that created output. Close this now. |
brownsarahm
added
the
status:wait
Member
|
I added some discussion points on #1933 |
ndporter
removed
the
status:wait
github-actions Bot
pushed a commit
that referenced
this pull request
May 1, 2026
Auto-generated via `{sandpaper}`
Source : 82e0f19
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2026-05-01 20:32:49 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : 70d1673
Branch : main
Author : Nathaniel D Porter <ndporter@vt.edu>
Time : 2026-05-01 20:30:47 +0000
Message : Merge pull request #1934 from sstevens2/issue-1933
cutting parts that duplicate welcome session
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
3 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.
This fixes #1933.
Thought this PR would help clarify our suggestions in that issue.