Tom,
I believe this is already in tsugi and tsugi-php for master:
If you are working in master - the PR process is different. All PRs need to go to tsugi. All of tsugi-php has been puled into tsugi in the lib folder.
Things are flipped - when I get a PR to tsugi, it is pushed back to tsugi-php through a subtree push so tsugi-php keeps up-to-date.
If you checkout tsugi for your systems, this makes things a lot simpler. I don’t know of a lot of folks that just use the tsui-php on a composer.json. Let me knos if you just use tsugi.
If you are back leveled (i.e. far behind master), we might need to do things differently. Let me know (a) if the existing patches are enough and (b) if you checkout tsugi or tsugi-php and (c) if you hang with master….
Thanks.
/Chuck
Hi Chris (and Dr Chuck),
We need the changes to be in the repository. I am happy to create a pull request for LTI13.php. However, just a question. Should that be a PR for the lib reposotory, and than somehow update the reference from the main repo to the lib repo and make a PR for that as well?
Cheers,
Tom