GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - splitrb/split-export: :open_file_folder: Split extension to export your data

BranchesTags
Open more actions menu

Latest commit

 

History

48 Commits
48 Commits

Folders and files

NameName
Last commit message
Last commit date
.github
.github
 
 
lib/split
lib/split
 
 
spec
spec
 
 
.gitignore
.gitignore
 
 
CODE_OF_CONDUCT.md
CODE_OF_CONDUCT.md
 
 
CONTRIBUTING.md
CONTRIBUTING.md
 
 
Gemfile
Gemfile
 
 
LICENSE
LICENSE
 
 
Rakefile
Rakefile
 
 
Readme.mdown
Readme.mdown
 
 
split-export.gemspec
split-export.gemspec
 
 

Repository files navigation

Split Export

An extension to Split to allow for easy exporting of AB testing data.

Requirements

The split gem and its dependencies.

Setup

If you are using bundler add split to your Gemfile:

gem 'split-export', :require => 'split/export'

Then run:

bundle install

Otherwise install the gem:

gem install split-export

and require it in your project:

require 'split/export'

Usage

This exports data for all experiments. This data set does not break down conversions by goals:

require 'split/export'
csv_data = Split::Export.to_csv
File.open('path/to/my.csv', 'w') {|f| f.write(csv_data) }

This exports data for a single experiment, and breaks it down by group and goal:

require 'split/export'
csv_data = Split::Export.experiment_to_csv("my_experiment")
File.open('path/to/my.csv', 'w') {|f| f.write(csv_data) }

Contribute

Source hosted at GitHub. Report Issues/Feature requests on GitHub Issues.

Tests can be ran with rake spec

Please conform to the Code of Conduct.

Note on Patches/Pull Requests

  • Fork the project.
  • Make your feature addition or bug fix.
  • Add tests for it. This is important so I don't break it in a future version unintentionally.
  • Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
  • Send me a pull request. Bonus points for topic branches.

Copyright

Copyright (c) 2013-2018 Andrew Nesbitt. See LICENSE for details.

About

📂 Split extension to export your data

libraries.io/rubygems/split-export

Resources

Readme
MIT license

Code of conduct

Code of conduct

Contributing

Contributing
Activity
Custom properties

Stars

7 stars

Watchers

2 watching

Forks

5 forks
Report repository

Releases

Sponsor this project

Packages

Used by

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.