Adding `features/readonly-ref` branch back
See original GitHub issueCan you please add the branch features/readonly-ref
of roslyn to the deployment?
This feature branch existed a few weeks ago and was of great use during development, but for some reason it was dropped in the current build. It would be great to have it back.
cc @ashmind
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
read only remote git branches that are existing
git for-each-ref --merged HEAD --format="%(refname:lstrip=2)" refs/remotes/origin. Both give me a list of remote branches but in this list are ...
Read more >Working with stacked branches in Git is easier with
In this post I discuss how to use the new Git rebasing feature, --update-refs, and how it makes working with stacked branches/PRs easier....
Read more >Git - Git References
Remote references differ from branches ( refs/heads references) mainly in that they're considered read-only. You can git checkout to one, but Git won't ......
Read more >bitbucket branch permission not working as it should
Any update? I have same issue. I try to make push and said I have no permission. If I remove permission branch and...
Read more >Feature branch workflow | GitLab
Feature branch workflow. To merge changes from a local branch to a feature branch, follow this workflow. Clone the project if you haven't...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@OmarTawfik Unfortunately I didn’t have time to look at it yet, want to finish my current feature work first and it is taking more effort than expected. However my next priority will be making sure the branches are properly available.
@ashmind I just checked out the feature branch on a new VM that has VS 15.1 (release) and it built correctly. Can you please tell me what is the issue you’re seeing?