<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[How to setup repository for collaboration?]]></title><description><![CDATA[<p dir="auto">So some friends and I all decided to work on a Magic Mirror together. We forked the Magic Mirror repository and are all working on it together. This means that we would all like to be able to develop it on our own personal computers and push to our forked repository, updating the config file as well as adding 3rd party modules. What would be the best way to setup the repository? Should we even fork the repository in the first place to allow for later updates? What .gitignore files should we edit? Thanks in advance.</p>
<p dir="auto">Note: I’m still fairly new to Github.</p>
]]></description><link>https://forum.magicmirror.builders/topic/6520/how-to-setup-repository-for-collaboration</link><generator>RSS for Node</generator><lastBuildDate>Fri, 10 Apr 2026 23:36:19 GMT</lastBuildDate><atom:link href="https://forum.magicmirror.builders/topic/6520.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 06 Feb 2018 02:19:24 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to How to setup repository for collaboration? on Tue, 06 Feb 2018 13:25:26 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mbeiswenger" aria-label="Profile: mbeiswenger">@<bdi>mbeiswenger</bdi></a> Suggest you take the free <a href="https://try.github.io/levels/1/challenges/1" target="_blank" rel="noopener noreferrer nofollow ugc">TryGit course</a>. You can also consult the <a href="https://git-scm.com/documentation" target="_blank" rel="noopener noreferrer nofollow ugc">Git documentation</a> and ask questions <a href="https://stackoverflow.com/questions/tagged/git" target="_blank" rel="noopener noreferrer nofollow ugc">here</a> (search first!).</p>
<p dir="auto">In terms of collaborating, it depends if you will all be working on the same or different features. You will want <em>at least</em> one fork. Also, make your commits small and related (not “here is MM3.0” but “added optional config param <code>capitalizeAll</code> to <code>newsfeed</code>“). You can either share contributor access to a single branch, or all have them fork-your-fork and submit Pull Requests to your fork/branch. You shouldn’t need to modify <code>.gitignore</code> – it should already ignore the right files plus a lot of OS-specific cruft.</p>
<p dir="auto">If you ever intend on submitting your changes to the MM <code>develop</code> (not <code>master</code>) branch, see the contributing notes in <a href="https://github.com/MichMich/MagicMirror/blob/master/.github/CONTRIBUTING.md" target="_blank" rel="noopener noreferrer nofollow ugc">Contributing.md</a>.</p>
]]></description><link>https://forum.magicmirror.builders/post/35316</link><guid isPermaLink="true">https://forum.magicmirror.builders/post/35316</guid><dc:creator><![CDATA[ninjabreadman]]></dc:creator><pubDate>Tue, 06 Feb 2018 13:25:26 GMT</pubDate></item></channel></rss>