Have Travis to modify/add commits to a PR - travis-ci

I have a C++ Github project and I would like to:
lower the boundary for people to contribute, but
keep the clang-format styling enforced
I am wondering if there is a way for me to have Travis to automatically apply (formatting) changes to people's PR. Looks like this is technically possible according to these github help pages, but I cannot find an example.
Has anyone ever tried this and could give me pointers? Or is there any project that already does this?

Related

Deciding which changesets go in Jenkins Build

I am trying to create a build in Jenkins, from certain changesets made in TFS.
I want to be able to decide which changesets should go in the build and which should be excluded.
I saw an earlier question How do you build from a specific TFS 2008 Changeset in Jenkins? which provided the answer using labels. Haven't tried it yet. But the question is 3 yrs old and I wanted to know if anyone has found an answer.
Any help would be appreciated. If it is not possible in Jenkins, please suggest any other tool that provides such functionality.
Atlassian Bamboo with TFS Repository Plugin
provides a solution for you :)
https://bitbucket.org/stellaritysoftware/tfs-repository-plugin/wiki/Home#!34-build-from-a-label-or-a-revision
BTW I've been looking around the tfs-plugin and although the docs doesn't mention "specific checkout by changeSet" I think there is a good chance that setting the VERSION_SPEC variable to change-set value, might do the trick for you.

How to link the issues in Bitbucket?

How to link the issues in Bitbucket?
I already use the milestone, component and version fields, but i need to mark issue as depend on #125 or blocked by #1220.
How?
Update
I can place link #1 in issue comment, of course, but:
Comments are scattered throughout the whole issue log.
Linked issue doesn't knowing about it.
So, I've search for linked issues\tickets fields, like Bugzilla/Mantis/OTRS do. Or Linked and Related in Stackoverflow itself.
UPDATED
Simply use the # and BitBucket will link automatically to the issue, as you know.
The linked issue isn't aware it was linked (as on GitHub, for example): it's the BitBucket behavior.

Creating an app as a Team so both parties can edit code

My friend and I are creating an app and we are wondering if there is a way where we can both edit the code at the same time?
Don't use SVN. You will see how easy version control could be and later everywhere on the job people will use Git because it is "better" and you will get frustrated.
Just use Git from the beginning, stay happy, you will love it. Really! 😏
The default in Xcode is Git too, so it can't be wrong.
Just be aware that the interface in Xcode is offering you a filtered version of the Git commands. As soon as you really need it for anything you will end up on the command line.
Whatever you try there, the first few times it will fail until you have learned the propper syntax and all side effects. So just make a copy of the folder, or zip or tar it before you try it a simple git command.
Also SourceTree is nice, but same problem there, learn what every command really does.
Use git! Lets people edit code and track the progress of the project (among many other useful tools).
Git Tutorial
If you are looking for more of a 'Google Docs' atmosphere, I would look into Codr or Cloud9
You can use SourceTree a free git repository handler.

TFS how to make quick code changes for production without undoing current changes

I'm not sure how to explain this question but I do know it's possible for what I want to achieve, I'm just not sure how to to it.
Lets say I'm working on a lengthy project in one of my solutions and the deadline isn't for a few more months but also need to make a changes to the same solution for some minor changes to go out into production before the other project is due. Obviously the code that's due for the project in a few months can't go out into to production because it could be catastrophic.
What's the best way to accomplish that? Would that be considered branching?
Thanks!
Yes, that's a branch.
Create a "hotfix" branch from the code that's currently running on production, fix the issue, check in and merge the changes back to "trunk", possibly upmerging the change to other branches (such as the one you're working on).
Of course the absolute quickest way would be to fix it on the "trunk" or main/head branch, but it sounds like you're already developing on that one.

Can Plastic SCM track code moved between files?

It seems that Plastic SCM does not track code moved between files (compare with e.g. Git) Am I right, or is there a way how to switch this feature on?
(Disclaimer: I work for Plastic SCM).
As far as I know git is able to track moved fragments of code between files when you run a "git blame", but it doesn't use this information during merge, correct? Git is able to calculate the "moved fragment" between files if it happens on the same commit and that's what it does while processing the 'blame'.
No, Plastic is not able to do that yet, which is a shame because we're already doing some interesting things around the idea:
First we have semantic method history which is able to track the history of a given method even when it has been moved, renamed and modified, but always inside the same file. We have plans to extend this to a repository wide basis, indeed we were about to implement it by the end of last year but we had to postpone it since we got some other highly requested features to work on.
The 'semantic method history' is based on the SemanticMerge tech we've developed. Right now it also works inside the file, but plans are also to come up with SemanticMerge multi-file (we even have a working prototype already). I expect this to be several steps ahead of what other tools can do.
Applying the last two together it wouldn't be hard to do something like 'blame with moved code', which as you pointed is something really great to have. Hopefully we'll release something like this in the coming months.

Resources