Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
GitLab allows to add comments / discussions to individual commits, which is very useful e.g. to ping someone with a quick question or ask for a review:
Is there any way to get a similar view for multiple commits?
Something like
https://myGitlabserver/myProject/myRepo/commit/12345+6789a+bcdef+13567
(^ doesn't work...)
I guess one possible workaround would be to git cherry-pick those commits to a temporary branch, temporarily revert them in the master branch, and then create a merge request... nasty.
What I'm looking for is an easy way to start a comment thread on a set of changes which already are in the master branch. So basically, I would like GitLab to virtually, but not physically, squash those commits together just for the sake of starting a comment thread on them.
Possible?
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 months ago.
Improve this question
Im working on the agile management system in GitLab.
For example i have issue X assigned to milestone #1, i couldn't finish it and would like to take it to the next milestone #2. In GitLab that's not possible to assign to multiple milestones. So I tried two scenarios :
Duplicate the issue and assign it to milestone 2
create a label that indicates that it belongs to the previous sprint What would you use? (it's weak because its gonna affect milestone #1 charts, completion percentage..etc)
Any suggestions?
How would you do it?
Issues can only be assigned to one milestone at most at any given time. You mentioned a few ways to handle this, which should work as well.
The way I've seen this typically handled is that you would change the milestone if you miss the original milestone target. To keep track of the fact that the issue belonged to a previous milestone, you can add a label like missed:old-milestone.
This is how GitLab handles its own issues and milestones.
For example, this GitLab issue was originally targeted for 15.2 milestone, but wasn't completed in time so its milestone was changed to 15.3 and the missed:15.2 label was added (both actions were taken automatically by a bot when the 15.2 milestone was closed).
This is a good practice, particularly when you use release versions or fixed-date milestones, because it becomes easy to see what issues actually make it into a particular release/milestone (important for communication/clarity). You can use the missed labels to figure out what work was planned for previous milestones but was missed.
As you pointed out, this will affect how metrics associated with your milestones are displayed. You may choose to snapshot your metrics before moving issues between milestones, if you want.
The approach you choose is a personal choice and the impact depends on exactly how you are using milestones.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
i am working on a website using polymer using Git ,now i need to remove and add feature to the website
so is the best way to do that :
forking the old website and edit/add/ remove feature .
starting new website from zero.
i was thing if i chose to fork i will get lot of messy code so what should i do?
Get yourself an structure plan draw.io
and think if you can create something like an internal api ( maybe overkill) or create modules of your features
Create an adittional diagram of your features and where these have connections to others.
Now create the fork and prepare your work before you implement new features
If your project gets bigger you maybe should get yourself an structure like the v-model
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I am creating an application where each user will have his own workspace which will consist of some text files. He will be editing and saving these files excessively.
I want to implement a version control system for each user to keep track of his work and revert back and forth to any previous version if he wants to.
I would also like users be able to fork into each others workspace to copy the content to their own workspace just like in plnkr.co, make changes and commit easily.
My stack is node.js and angular.js
Where should I start, to implement it. I guess there should some way to use git or some other open source project. Does anybody have any idea what plunker is using?
Super late response, but for anyone stumbling across this, try checking out git=annex
We used this at one of my old jobs for keeping track of fMRI datasets. It's best used for large data though, so one may want to find something similar but perhaps better aligned for what they need.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am reading the code of vim 1.14 and I have some questions about undo.c.
I don't understand the implementation of the undo/redo operation, especially in the function u_undoredo().
I want to know why it uses the link list u_entry?
If you checkout the latest version of vim there is an explanation of vim's undo/redo implementation at the top of the undo.c file.
You can read it here.
Each u_entry list contains the information for one undo or redo.
A linked list would make sense for an undo/redo implementation to use since each entry only needs to reference the next or previous entry and can easily be added to efficiently. This is also why vim's undo history creates multiple branches of undo history. Beyond that, I'm not sure what your question is.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Kind of a stupid question, but I'm just covering my bases and I haven't found anything with a quick google search. I have an rsync that runs hourly and is kicked off by a cron. Then once a week I need kick this rsync off from another script to make sure I have the latest files I need.
What happens if the rsync is already running from the cron and I kick the same rsync off again? In a quick test it looks like the second rsync picks up where the first left off, but I want to be sure so I thought I would ask.
Each rsync will run independently and will take their own "snapshots" of the local and remote sides to compare. I think in many cases where you are just pushing updates from one side to the other you will probably be fine, the only caveat being you many end up transferring duplicate data.