Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0p4
2017.1.0b8
2017.1.0f1
Issue ID
974320
Regression
No
[Collab] Commit message is lost if another team member pushed changes while writing commit description
To reproduce:
1. Create a new project
2. Push to Collab
3. Download project on 2nd machine
4. Create script on both machines
5. Write commit message on 1st machine
6. Push changes on 2nd machine
7. Update project on 1st machine
8. Open Collab toolbar
Expected vs actual: after 8th step commit message on the 1st machine should not be lost
Reproduced on: 2017.1.2p4, 2017.2.0p4, 2017.2.0f2, 2018.1.0a7
Not reproducible: 5.6.4p4
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
We will be redesigning the Collab Toolbar in the near future. We are closing all low-priority Toolbar-related bugs as Won't Fix so that we can properly focus on the new design rather than spending more time hotfixing the current Toolbar.