Create GitHub releases with assets
Publish release notes to Gitea
CLI to increment a project's version and optionally publish release to Github/Gitea
A plugin for semantic-release which publish release notes in a Microsoft Teams channel
Publish release notes to Gitea
A plugin for semantic-release which publish release notes in a Google Chat
publish release of x-cmd organization
Publishing workflow commands for kodrdriv (development, publish, release)
publish release of x-cmd organization
publish release of x-cmd organization
publish release of x-cmd organization
Publish Release Notes to Slack seamlessly
publish release of x-cmd organization
publish release of x-cmd organization
CLI tool to publish release notes to Notion databases with markdown support
publish release of x-cmd organization
publish release of x-cmd organization
publish release of x-cmd organization
publish release of x-cmd organization
publish release of x-cmd organization
publish release of x-cmd organization
publish release of x-cmd organization
publish release of x-cmd organization
publish release of x-cmd organization
Shared functionality for configuration of jwt authentication for Rust services
An example showcasing the usage of https://github.com/PRO-2684/rust-template.
A IDL codegen.
A IDL codegen.
A IDL codegen.
A IDL codegen.
A IDL codegen.
A IDL codegen.
A IDL codegen.
A IDL codegen.
A IDL codegen.
A IDL codegen.
openMSX-Builder is used for building the latest SVN checkouts of openMSX and openMSX-Debugger from their sourceforge repository. It also supports publishing the created builds to an external location via scp, announcing successfully published builds via Twitter and reporting build-errors via e-mail.
A system to make it easier to manage and monitor cron jobs. Please note new versions are no longer published to rubygems but https://github.com/jamesrwhite/minicron/releases instead.
Buildar helps automate the release process with versioning, building, packaging, and publishing. Optional git integration.
release-gems action automates gem release workflow: build, attestation and publish
release-gems action automates gem release workflow: build, attestation and publish
Manages the full release lifecycle of Metanorma documents: discover compiled documents, extract metadata, detect changes, package as zip, publish to platforms (GitHub Releases, GitLab, local filesystem), and aggregate published releases into index.json with a file tree for any site generator.
When you want to publish a post, but not promote it yet on your welcome page, you might want to call it 'released'.
Toys-Release is a Ruby library release system using GitHub Actions and Toys. It interprets conventional commit message format to automate changelog generation and library version updating based on semantic versioning, and supports fine tuning and approval of releases using GitHub pull requests. Out of the box, Toys-Release knows how to tag GitHub releases, build and push gems to Rubygems, and build and publish documentation to gh-pages. You can also customize the build pipeline and many aspects of its behavior.
A corundum is a synthetic gemstone - including synthetic rubies. Ergo: a tool for synthesizing gems. Corundum starts with the outlook that gemspecs are relatively easy to work with, and that the opinion of the RubyGems team is that they should be treated as a configuration file, not a code file. Furthermore, Rake is a powerful, easy to use tool, and does admit the use of Ruby code to get the job done. The hard part about publishing gems is getting them into a state you'll be proud of. There's dozens of fiddly steps to putting together a gem fit for public consumption, and it's very easy to get some of them wrong. Corundum is a collection of Rake tasklibs, therefore, that will perform the entire process of releasing gems, including QA steps up front through packaging and releasing the gem
# Squash Migrations Periodically squash migrations to reduce overhead of the `db:migrate` Rake task. ## Creating a release 1. Create a new pull request that: - Bumps the version in `rails-squash-migrations.gemspec` - Updates `CHANGELOG.md` to include all noteworthy changes, the release version, and the release date. 2. After the pull request lands, checkout the most up to date `main` branch and build the gem: ```console $ docker run --rm -it -v $(pwd):$(pwd) -w $(pwd) ruby gem build ``` 3. Publish the gem: ```console $ docker run --rm -it -v $(pwd):$(pwd) -w $(pwd) ruby gem push rails-squash-migrations-X.Y.Z.gem ``` 4. Create and publish a git tag: ```console $ git tag X.Y.Z $ git push https://github.com/Pioneer-Valley-Books/rails-squash-migrations.git X.Y.Z ```
= dm-is-published This plugin makes it very easy to add different states to your models, like 'draft' vs 'live'. By default it also adds validations of the field value. Originally inspired by the Rails plugin +acts_as_publishable+ by <b>fr.ivolo.us</b>. == Installation # Add GitHub to your RubyGems sources $ gem sources -a http://gems.github.com $ (sudo)? gem install kematzy-dm-is-published <b>NB! Depends upon the whole DataMapper suite being installed, and has ONLY been tested with DM 0.10.0 (next branch).</b> == Getting Started First of all, for a better understanding of this gem, make sure you study the '<tt>dm-is-published/spec/integration/published_spec.rb</tt>' file. ---- Require +dm-is-published+ in your app. require 'dm-core' # must be required first require 'dm-is-published' Lets say we have an Article class, and each Article can have a current state, ie: whether it's Live, Draft or an Obituary awaiting the death of someone famous (real or rumored) class Article include DataMapper::Resource property :id, Serial property :title, String ...<snip> is :published end Once you have your Article model we can create our Articles just as normal Article.create(:title => 'Example 1') The instance of <tt>Article.get(1)</tt> now has the following things for free: * a <tt>:publish_status</tt> attribute with the value <tt>'live'</tt>. Default choices are <tt>[ :live, :draft, :hidden ]</tt>. * <tt>:is_live?, :is_draft? or :is_hidden?</tt> methods that returns true/false based upon the state. * <tt>:save_as_live</tt>, <tt>:save_as_draft</tt> or <tt>:save_as_hidden</tt> converts the instance to the state and saves it. * <tt>:publishable?</tt> method that returns true for models where <tt>is :published </tt> has been declared, but <b>false</b> for those where it has not been declared. The Article class also gets a bit of new functionality: Article.all(:draft) => finds all Articles with :publish_status = :draft Article.all(:draft, :author => @author_joe ) => finds all Articles with :publish_status = :draft and author == Joe Todo Need to write more documentation here.. == Usage Scenarios In a Blog/Publishing scenario you could use it like this: class Article ...<snip>... is :published :live, :draft, :hidden end Whereas in another scenario - like in a MenuItem model for a Restaurant - you could use it like this: class MenuItem ...<snip>... is :published :on, :off # the item is either on the menu or not end == RTFM As I said above, for a better understanding of this gem/plugin, make sure you study the '<tt>dm-is-published/spec/integration/published_spec.rb</tt>' file. == Errors / Bugs If something is not behaving intuitively, it is a bug, and should be reported. Report it here: http://github.com/kematzy/dm-is-published/issues == Credits Copyright (c) 2009-07-11 [kematzy gmail com] Loosely based on the ActsAsPublishable plugin by [http://fr.ivolo.us/posts/acts-as-publishable] == Licence Released under the MIT license.
= Barcode Creating barcodes (at the moment only Interleaved2of5). == Usage Create the barcode string and the barcode graphics data i2o5 = Interleave2of5("01199") code = i2o5.encode barcode = i2o5.barcode pdf = Prawn::Document.new barcode.to_pdf(pdf) When used with rails add require 'interleave2of5' to config/application.rb The barcode can be used to create a graphical representation of the barcode. == Release Notes * Version 0.0.1 Create barcode Interleaved 2 of 5 that can be added to a pdf file * Version 0.0.2 Fix check digit calculation * Version 0.0.3 Add valid? to check whether a decoded value (e.g. by a barcode scanner) is valid == Licencse Barcode is published under the MIT license
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.