-
Notifications
You must be signed in to change notification settings - Fork 8
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
Test GitHub comment persistence #2
base: master
Are you sure you want to change the base?
Conversation
Added some line and commit comments |
f49c96e
to
cc19d23
Compare
OK after rebase, it looks like f49c96e (unqualified SHA hash) doesn't show the comments but tlyu/krbdev-services@f49c96e might? Weird. |
@@ -13,3 +13,6 @@ svnhooks/ | |||
Hook scripts for our Subversion repositories. This set comes | |||
from the krb5 repository; krb5-appl might have a slightly | |||
different set of scripts. | |||
|
|||
test1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commenting on lines on the pull-request diff (the "files changed" tab) are supposed to remain persistent even if the commits involved change. "kaduk commented on an outdated diff", etc..
1e77638
to
1d4c099
Compare
Weird, your line comments got preserved after rebase and mine (on a different commit) didn't. |
That's because I wasn't commenting on a commit -- I was commenting on the diff associated with the pull request. (The UI for finding this is rather poor.) |
|
||
test1 | ||
testfoo | ||
test2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test another line comment
1d4c099
to
9fbf749
Compare
9fbf749
to
4de1eba
Compare
No description provided.