Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration to Github #5

Closed
fortizpenaloza opened this issue Nov 21, 2018 · 15 comments
Closed

Migration to Github #5

fortizpenaloza opened this issue Nov 21, 2018 · 15 comments

Comments

@fortizpenaloza
Copy link
Collaborator

Hi, are you planning to migrate the project to Github?

Can I help?

@zeroflag
Copy link
Owner

Hi @fortizpenaloza,

Yes, it would be great to have the source here. Any help is appreciated.

Attila

@fortizpenaloza
Copy link
Collaborator Author

See #6

zeroflag pushed a commit that referenced this issue Nov 27, 2018
@fortizpenaloza
Copy link
Collaborator Author

I did the v2.6.0 release, matching the one in Smalltalkhub.

I tried to add the Travis and Coveralls integrations but it seems you will have to do it as it can only be done by the owner.

@zeroflag
Copy link
Owner

How can I do that?

@fortizpenaloza
Copy link
Collaborator Author

I forgot to mention that the required files are ok, you need to go to https://travis-ci.com and https://coveralls.io/ and follow the instructions to integrate them.

@zeroflag
Copy link
Owner

I added it to travisci: https://travis-ci.com/zeroflag/Teapot but I noticed there is already a https://travis-ci.com/fortizpenaloza/Teapot which seems to be working too. What can mine do what yours cant ?

@gcotelli
Copy link
Contributor

Travis will run only for the "forks" that has enabled the integration. So for example if only the @fortizpenaloza fork is enabled new builds on this repository will not run unless he upgrades his own fork .

@zeroflag
Copy link
Owner

@gcotelli I see thanks, I updated the urls to mine.

@fortizpenaloza
Copy link
Collaborator Author

Great news!

Thanks, @gcotelli.

It also opens a lot of tools, for example, now you can protect master branch and configure your repo merging policy so (even including you) must fix all test before merging a PR against master.

And with Coveralls you can ask collaborators to mantain the coverage level.

@gcotelli
Copy link
Contributor

I've added #7 fixing the URLs in the badges, because it were referencing @fortizpenaloza fork

@zeroflag
Copy link
Owner

@gcotelli I was quicker :)

@gcotelli
Copy link
Contributor

#8 , the LICENSE file was missing.

@fortizpenaloza
Copy link
Collaborator Author

#8 , the LICENSE file was missing.

done!

@fortizpenaloza
Copy link
Collaborator Author

@zeroflag can you send an email to pharo mailing lists to announce it? Then I think we can close this issue.

@zeroflag
Copy link
Owner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants