Hot answers tagged

10

It's always good to have a dedicated branch for each Pull Request you are going to make. One of the simplest ways to create a up-to-date new branch is to just use the GitHub web gui to edit the file in the original repository. When saving, GitHub will automatically create a new branch in your fork based on the branch you currently edit. If you want to edit ...


8

There are two concepts we're dealing with, the first being a code repository. Although there are different types of repository technologies, GIT is the defacto standard currently. Websites such as Github and Bitbucket are popular web services offering free GIT hosting solutions. The key point here being GIT is the actual underlying technology, and will ...


4

One big thing that helps with grouping your contributions is to move each contribution into a separate, appropriately named, branch. If you're adding a feature, use a prefix like feature- and the add a one or two word feature description for the branch name. If it's a bug fix in the JForm class, use bugfix-jform. This makes it really easy to identify what ...


4

You can of course use it for your website and is an amazing tool to track everything. You can make your js changes and commit them so you can revert only your js changes. You need to first setup a GIT Repo see: https://help.github.com/articles/create-a-repo/ Once setup you can import all the files of your current working site. Once imported you can ...


3

One approach I read about to making your component a proper format for versioning and zipping is this: Take a copy of your component and install it; Remove the installed component folders within your Joomla installation (administrator/components/com_component, components/com_component, media/com_component); Then create symbolic links from those folders to ...


3

You did not mention which editor you are using. However most editors such as Eclipse supports ANT build files and can automatically build whenever any change done to the source code. So here is how I do my development. I use separate workspace for all my projects I structure my component like what you mentioned in your last code block i.e. only the ...


2

I believe you are applying the patch incorrectly. To properly install git patches, you will need to perform a few command line functions which are explain in the following tutorial: https://ariejan.net/2009/10/26/how-to-create-and-apply-a-patch-with-git/ Personally I think you could simply perform the change manually as there are only minor tweaks ...


2

Current status: proof of concept, not publicly released. History I started working on my own solution, with the temporary name of gitcms. Here is the architecture in a nutshell: This is how it works: Github repository Each time a commit is pushed the repository, and event will be triggered. It is possible to catch this event using a webhook which ...


2

As far as I can see the only way to really get the information in a repository is manually, unless you want to look through the commits and all, figuring out what goes where. Though either way it would be best to have a copy of the repo somewhere (auto pull updates and all that, so it would have local files in raw format). So the best way is to have a ...


2

To set files and directories to chmod 777 or even chmod 770 is not a good idea on a production system. Every webserver system like apache2, nginx can be configured to work with a special user and group - that's important not to get any user rights on the system. On most Debian like systems, the user is set to www-data with group www-data, standard is the ...


2

Yes, you can put the update.xml in the main repository. As for the link to provide JED, you'll need to open the file on Github, then click "Raw", so you URL will look something like this: https://raw.githubusercontent.com/USER/REPO-NAME/master/path-to-file/update.xml And also be sure to reference this URL in your extension's XML file too.


1

You will need to download and install Composer first. Once done, open your terminal, navigate to the root of your Joomla installtion, and type in the following command: composer install You'll then need to install NodeJS. Be sure to get the long term release 10.x. Once installed, in the same terminal, run the following command: npm i These commands ...


1

You can use a tool mostly designed for testing purposes under Joomla: com_patchtester You can directly search after the Pull Request id: 6180.


1

If it was me, I'd retrieve using whatever method suits you (file_get_contents maybe, I like curl, but whatever) and then use the Parsedown class to turn it into HTML. http://parsedown.org/ Joomla has its own github class, but I haven't looked to see what it actually does.


Only top voted, non community-wiki answers of a minimum length are eligible