<commit_before>Feature: User frontend
	In order to use API provided by this library properly
	I need to use provided set of objects
  
	Background:
		Given the "User" resource

	Scenario: Existence of User class
		Given I am trying to make use of this library
		Then "User" resource should exist
	
	Scenario: Existence of User resource
		Given the "User" resource
		Then the object should exist
	
	Scenario: User's name
		Given the "name" property
		Then the property should be "<NAME>"
		And the property should be writable
	
	Scenario: User's location
		Given the "location" property
		Then the property should be "San Francisco"
		And the property should be writable
	
	Scenario: User's company
		Given the "company" property
		Then the property should be "GitHub"
		And the property should be writable
	
	Scenario: User's login
		Given the "login" property
		Then the property should be "defunkt"
		And the property should not be writable
	
	Scenario: User's bio
		Given the "bio" property
		Then the property should be "The greatest and best programmer in the world."
		Then the property should be writable
	
	Scenario: User's email
		Given the "email" property
		Then the property should be "<EMAIL>"
		And the property should be writable
	
	Scenario: User's hireable status
		Given the "hireable" property
		Then the property should be true
		And the property should be writable
	
	Scenario: User's blog
		Given the "blog" property
		Then the property should be true
		And the property should be writable
	<commit_msg>fix the blog property value in User feature<commit_after>Feature: User frontend
	In order to use API provided by this library properly
	I need to use provided set of objects
  
	Background:
		Given the "User" resource

	Scenario: Existence of User class
		Given I am trying to make use of this library
		Then "User" resource should exist
	
	Scenario: Existence of User resource
		Given the "User" resource
		Then the object should exist
	
	Scenario: User's name
		Given the "name" property
		Then the property should be "<NAME>"
		And the property should be writable
	
	Scenario: User's location
		Given the "location" property
		Then the property should be "San Francisco"
		And the property should be writable
	
	Scenario: User's company
		Given the "company" property
		Then the property should be "GitHub"
		And the property should be writable
	
	Scenario: User's login
		Given the "login" property
		Then the property should be "defunkt"
		And the property should not be writable
	
	Scenario: User's bio
		Given the "bio" property
		Then the property should be "The greatest and best programmer in the world."
		Then the property should be writable
	
	Scenario: User's email
		Given the "email" property
		Then the property should be "<EMAIL>"
		And the property should be writable
	
	Scenario: User's hireable status
		Given the "hireable" property
		Then the property should be true
		And the property should be writable
	
	Scenario: User's blog
		Given the "blog" property
		Then the property should be "http://chriswanstrath.com/"
		And the property should be writable
	
{'fraction_non_alphanumeric': 0.04220360824742268, 'fraction_numerical': 0.0, 'mean_word_length': 3.806501547987616, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7627010', 'n_tokens_mistral': 952, 'n_tokens_neox': 814, 'n_words': 451}