Repository navigation
Introduce CI - #2
Conversation
|
Here is builds hannesa2#1 unfortunately in upstream not. @jspiro Do you have access to Any improvements are welcome ! I just begin to work with Xcode |
|
Puhh, everyone make a new fork of a fork of a fork ... Do we need the changes of https://github.com/chbeer/MGScopeBar.git as well ? |
|
I've fixed up the permission at the org-level, so you should have access now. |
jspiro
left a comment
There was a problem hiding this comment.
That's shockingly straightforward! Once this works for PRs, should we make a workflow for this too when we prepare a release, or have this also do a build upon merge (where are the artifacts stored?)?
| @@ -0,0 +1,25 @@ | |||
| name: PullRequest | |||
There was a problem hiding this comment.
| name: PullRequest | |
| name: build-mgscopebar |
There was a problem hiding this comment.
With it, copy&paste needs some more work in the future 😉
|
I've enabled branch protection – after merge, please enable the requirement for this check to succeed: https://github.com/gitx/MGScopeBar/settings/branch_protection_rules/19113317 |
I would make a workflow for a release (if required) but first I want to have the pull request flow done |
Of course, of course. After! |
| project: MGScopeBar.xcodeproj | ||
| scheme: MGScopeBar | ||
| configuration: Release | ||
| action: archive |
There was a problem hiding this comment.
Is archive or is build better ?
There was a problem hiding this comment.
Archive seems like a good idea, as it packages it up?
There was a problem hiding this comment.
I didn't check. Are there tests as well to run ?
Sorry, I don't now how to find it in Xcode. Maybe you tell it me
|
Ok, I applied renames |


My plan it to introduce in each submodule CI first, and then in https://github.com/gitx/gitx
This is a pre-task to switch to target
10.9