These are chat archives for BSData/wh40k
Good questions @alphalas I have a little one, how often should I commit? Last night I fixed the problem with the eldar core command auxiliary selections not showing, but I was battling with the min/max limits so I didn't commit... Should I have?
It's best to commit whenever you fix any bug/issue completely, or some part that is decoupled (say a bug is in 3 cats, you've fixed it in one of them), and push changes immediately (as long as you know you've fixed it, so test what you're fixing ;) ). That way there is less chance of any conflict.
should the selected thing be a entry? or should it be a profile like the pistol below it?
The Hot Shot Lasgun here is a very bad design. There shouldn't be entries that link to entries of the same name, as is the case here. The Lasgun should be linked directly as a child of parent group instead of being nested in an entry itself.
Using my godly admin powers, I've single-handedly reset these revisions. Hopefully I've not hurt any feelings, if so, please accept my apologies.
Case is closed. For future reference, please make any new catalogues start with revision 2000, and the same when any catalogue is upgraded to 2.0 format.
alright. It reverted the entire commit with all 4 files and pushed them. That undid my mistake - but also my work.
Now how do I get it to revert the revert on the DA cataloque only?
Oh how I long for my simple svn/tortoise setup...