markrmiller commented on pull request #365:
URL: https://github.com/apache/lucene/pull/365#issuecomment-941999570


    Yeah, unrelated to anything but the water cooler, another branch makes the
   most sense, but I had unusual alterior motives to start using an
   organization for a few things.
   
   * my personal repo is a bit of a mess of 10 years of random crap with repos
   full of random branches and what not.
   
   * it's a pain to easily just clean up because it's unclear what has no
   value and what I might want around and would take some time to make good
   progress
   
   I'd like to transition to a more clean, organized space.
   
   An organization let's me jump start a bit to a space like that and slowly
   work out the personal space.
   
   That likely would not have been enough to get me to do this alone, but I
   also ran into a feature I wanted to trial a bit that I could not. GitHub's
   codespaces requires an org unless you got into the Beta for now. I've tried
   hosting code-server locally which is cool, but don't like running services
   with external access, so perhaps giving codespaces a test tipped me over.
   You can turn your personal account into an org, but you have to lose
   everything or something.
   
   Mark
   
   On Tue, Oct 12, 2021 at 3:45 AM Uwe Schindler ***@***.***>
   wrote:
   
   > I only recently learned that while Apache has unlimited action minutes,
   > they do have limited throughput for the whole organization and I don't want
   > to eat them here.
   >
   > I learned about this, too. A simpler trick for this is to use 2 branches
   > in your markmiller repo. When I prepare pull requests, I also do this
   > often. Start in a branch with some random internal name. Before I open the
   > pull request, I create a new branch named after the Lucene issue number and
   > create the pull request. Theoretically you can use your first branch for
   > further development and just merge into the official
   > Lucene-issue-number-branch.
   >
   > —
   > You are receiving this because you authored the thread.
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/lucene/pull/365#issuecomment-940798656>, or
   > unsubscribe
   > 
<https://github.com/notifications/unsubscribe-auth/AADNSFD2ZHFVTO2OFAJHWYTUGPYRXANCNFSM5FQRHPMA>
   > .
   >
   -- 
   - MRM
   


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org

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



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

Reply via email to