KevinGG commented on pull request #12996: URL: https://github.com/apache/beam/pull/12996#issuecomment-703856209
> > > I would just use a tag. The only purpose of a release branch is cherrypicking and continuing to do point releases. > > > > > > Thanks Kenn. > > @aaltay, could you please help me add a tag such as `jupyterlab-sidepanel-v1.0.0` when/after merging this PR? > > I could not send a tag through a PR. > > TL;DR: You could also use jlpm (yarn) to auto generate a tag: > > ``` > > jlpm config set version-tag-prefix "jupyterlab-sidepanel-v" > > jlpm version # Then input 1.0.0, it should auto generate a git tag for you. > > ``` > > > > > > Thanks! > > I do not have jlpm. I guess I can clone the repo, and tag the specific commit and push. I do not know if there is an easier way to do this. Can I create a tag on github UI? I think a tag is like a commit, you can use below command ``` git tag -fa jupyterlab-sidepanel-v1.0.0 -m "Extension: apache-beam-jupyterlab-sidepanel version 1.0.0" <this PR merge commit's hash> git push origin(or upstream, whichever is the apache/beam remote) jupyterlab-sidepanel-v1.0.0 ``` ---------------------------------------------------------------- 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: [email protected]
