MRIIOT
MRIIOT
These are the two structures available. https://github.com/Ladder99/fanuc-driver/blob/12301dad1ca31ccb6e3dafcfcfbdf13bfede95c2/fanuc/fwlib.cs#L3319-L3354
fwlib.cs does need to be refactored.
Would capturing the docker traffic help in this case? https://github.com/siemens/edgeshark
> 6. backlog issues are something we want to do, but they are not a priority and the devs should not work on them unless approved by @MRIIOT, however, commenting...
Ok, so options are: - proposed -> declined - proposed -> backlog - backlog -> approved - approved -> wip ? This is fine with me. backlog then seems to...
> application:$appName: > description: Anything related to a specific application; > rules: whenever the issue is related to a specific application which name is part of the label after colon;...
> I use categories/labels as the first part of a title so they can be sorted into groups, and it's easy to see at a glance what category an issue...
> What would be the use case for use case labels? > > Are they to be used as customer feature requests? Then I suggest to use enhancement label. >...
> > we could create as many labels as makes sense to categorize issues > > Yes and no. The more labels we have, the harder it’ll be to maintain...
Where do the changes need to happen?