The fact that a log is initially cloned from another log is not preserved in the revision history of the new log. It would be easy to include this, and add useful context to the history of the records.
Set the log revision message on newly cloned logs to say "Cloned from log [original-log-id]"
Implement.
Revision log of cloned logs will indicate that they were cloned.
None.
None.
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
m.stentaThis is related to but different from: #3358971: Add link to cloned logs in status message
Comment #3
m.stentaAh I actually forgot we considered this in the past and added a textarea to the confirmation form for an optional revision message in #3258268: Add revision message field to actions. This applied to both the "reschedule" and "clone" actions.
The reasoning was:
Some thoughts:
Proposal:
Comment #4
m.stentaGeneralizing the title of this issue.
Comment #5
m.stentaComment #7
m.stentaComment #8
m.stentaI don't understand why tests are failing...
Comment #9
m.stentaThese tests are passing when I run them locally, so I'm wondering if this is an issue with the Drupal.org Gitlab test runner... 🤔
Comment #10
m.stentaI figured out what was happening. The strings being compared have links in them, which are not represented in the diff I pasted above. I found another diff that shows the full string:
Pushed a fix that should respect the path prefix being applied in Drupal.org testing environment...
Comment #11
m.stentaComment #12
m.stentaI've decided I'm going to wait until #3578407: Start 4.x branch to merge this.
Comment #13
m.stentaComment #14
m.stentaComment #18
m.stenta