Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / zendesk/arturo issues and pull requests

#25 - Add global features

Pull Request - State: closed - Opened by plukevdh over 12 years ago - 1 comment

#24 - Recipient-less features

Pull Request - State: closed - Opened by plukevdh over 12 years ago - 6 comments
Labels: Feature

#23 - Does not work on ActiveRecord 3.2

Issue - State: closed - Opened by staugaard almost 13 years ago - 5 comments
Labels: rails 3.1+

#22 - Fix typo

Pull Request - State: closed - Opened by trotter almost 13 years ago - 2 comments

#20 - Feature bit cache warming

Pull Request - State: closed - Opened by kbuckler almost 13 years ago - 6 comments

#19 - Add license info to repository.

Issue - State: closed - Opened by vhodges over 13 years ago - 1 comment

#18 - Quick question: What license (if any) is arturo license under?

Issue - State: closed - Opened by vhodges over 13 years ago - 2 comments

#17 - Add caching of features

Issue - State: closed - Opened by jamesarosen over 13 years ago - 3 comments

#16 - Add Arturo::Feature::Phased mixin

Issue - State: closed - Opened by jamesarosen almost 14 years ago - 1 comment
Labels: Feature

#15 - Move enable_feature! and disable_feature! into Arturo::TestSupport

Issue - State: closed - Opened by jamesarosen almost 14 years ago - 1 comment

#14 - Add Arturo.foo_enabled_for?(feature_recipient) helper

Issue - State: closed - Opened by jamesarosen almost 14 years ago - 3 comments
Labels: Feature

#13 - Page errors + tests

Pull Request - State: closed - Opened by plukevdh almost 14 years ago - 3 comments

#12 - HTML escaped

Pull Request - State: closed - Opened by plukevdh almost 14 years ago

#11 - add module-level helper method to check whether a feature is enabled

Issue - State: closed - Opened by jamesarosen about 14 years ago - 1 comment

#10 - Provide Arturo.enable_feature! and Arturo.disable_feature! for tests

Issue - State: closed - Opened by jamesarosen about 14 years ago - 1 comment

#9 - All features are rolled out to feature recipients in the same order

Issue - State: closed - Opened by jamesarosen about 14 years ago - 1 comment

#8 - Can I deploy some features on a per-user basis and others on a per-account basis?

Issue - State: open - Opened by jamesarosen about 14 years ago - 15 comments

#7 - creating a new feature does not save deployment percentage

Issue - State: closed - Opened by jamesarosen about 14 years ago - 1 comment
Labels: CRUD

#6 - error messages show escaped HTML

Issue - State: closed - Opened by jamesarosen about 14 years ago - 2 comments
Labels: rails 2.3

#5 - Stop Feature and FeaturesController from reloading in development

Issue - State: closed - Opened by jamesarosen about 14 years ago - 1 comment
Labels: rails 2.3

#4 - Provide a sane default for Arturo.feature_recipient

Issue - State: closed - Opened by jamesarosen about 14 years ago - 1 comment

#3 - replace Arturo.permit_management with a FeatureManagement mixin

Issue - State: closed - Opened by jamesarosen about 14 years ago - 1 comment

#2 - "thing_that_has_features" is confusing terminology

Issue - State: closed - Opened by jamesarosen about 14 years ago - 4 comments

#1 - Replace Arturo.permit_management with a :manage_features feature and a whitelist

Issue - State: closed - Opened by jamesarosen about 14 years ago - 2 comments