gerrit - Project Hosting on Google Code
Gerrit is a web based code review system, facilitating online code reviews for projects using the Git version control system.
Related cards:
wkhtmltopdf - Project Hosting on Google Code
Simple shell utility to convert html to pdf using the webkit rendering engine, and qt.
wkrte - Project Hosting on Google Code
WKRTE is a jQuery rich text editor based on lwrte by plandem.
rest-client - Project Hosting on Google Code
RESTClient is a Java application to test RESTful webservices. It can be used to test variety of HTTP communications.
jspdf - Project Hosting on Google Code
jsPDF is an open-source library for generating PDF documents using nothing but Javascript. You can use it in a Firefox extension, in Server Side Javascript and with Data URIs in some browsers.
How to push to Git without running CI on GitLab CI, GitHub Actions, or Travis CI
If a project ist configured to spawn CI runners for tests or deployment when pushing to the Repo, a habit of pushing WIP commits regularly may conflict with that.
Here are two solutions that allow you to keep pushing whenever you feel like it.
#...
cortesi - The impact of language choice on github projects
Are there major differences between projects in different languages? Is it possible to quantify these differences? I decided to try to gather some hard numbers.
Lightning Talk: Coverage based Test Case Prioritization in Ruby on Rails
For my computer science bachelor's thesis I programmed and evaluated a CLI Test Case Prioritization (TCP) tool for makandra. It has been written as a Ruby Gem and was tested and evaluated against one Ruby on Rails project....
Google Summer of Code winner: ActiveModel for Ruby on Rails
Finish the remainder of the ActiveModel todo list (observers, callbacks, validations, scoping, and serialization) in addition to associations. Also wire up ActiveModel up to ActiveRecord and ActiveResource.
geewax.org | Agile git Workflow
When we started using git to manage our source code at work, we actually jumped in a little bit too fast. It seems like there is a lot of writing about how you can do lots of really neat things with git, but no real guide about one particular way ...
How to write modular code
Or: How to avoid and refactor spaghetti code
Please note that I tried to keep the examples small. The effects of the methods in this card are of course much more significant with real / more complex code.