Test modifications to Jenkins Pipeline shared library without needing a commit

Question

Scenario: I have a JenkinsFile in a project that references code in a shared pipeline library using @Library('my-lib') syntax. I would like to test changes to my library function without needing to perform a commit to my library repo.

I realize that I can target a specific version or branch of the library in my include statement. I also realize that I can modify the script in my JenkinsFile without needing a commit by using the "Replay" functionality in the Jenkins UI. How can I test modifications to the shared library code without needing to do a commit to my branch that I'm testing in? Right now, we're having to perform a commit with each tweak to our library code, and we'd prefer not to have a super gross commit history. In other words, we only want commits to our library repo for code that we know is working.