[GitHub] [lucene-solr] epugh commented on pull request #2016: SOLR-14067 v2 Move Stateless Scripting Update Process to /contrib/scripting module

[GitBox <gi...@apache.org>]

epugh commented on pull request #2016:
URL: https://github.com/apache/lucene-solr/pull/2016#issuecomment-761566739


   I am definitly struggling with branches, keeping up with master.   Clearly there is something I don't understand about the workflow with Git.   Plus, I'm very nervous about anything I do..  The idea of doing a "force push" makes me nervous I'm going to mess up everything for everybody.   Makes me think I need to invest time in properly learning how to use Git.  
   
   When I look at folks code, I typically just bring up the files changed view, in this case: https://github.com/apache/lucene-solr/pull/2016/files and then scroll through.  
   
   I wonder if, at this point, the right thing to do is just extract a .patch file, add that back to the ticket, and then apply that to master, and abandon this branch.   Folks have provided lots of great review through this journey on this branch, but now I don't know that we need it anymore.   
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org