Completing your development and releasing to production

By now, you should have quite a few modified files in your development branch. As part of your development process, you should be committing changes and pushing them back to GitHub on a regular basis. As we discussed earlier in this chapter, you should be testing your code after every 20 or so lines that you add or change in your code. You should also be committing your changes after each time you successfully test them. By regularly pushing your changes to GitHub, it allows other developers to make sure that your work is not affecting any changes they are making to the same code base. As well, it allows them to help out with your development branch when needed. To push our changes back to ...

Get Learning Splunk Web Framework now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.