Remove Berksfile.lock from dev branches
blueprint remove-berksfile-lock-from-dev-branches Change-Id: I4d9643b7739446943d648a7e9a6d4bb6e9ad0c63
This commit is contained in:
		
							
								
								
									
										10
									
								
								README.md
									
									
									
									
									
								
							
							
						
						
									
										10
									
								
								README.md
									
									
									
									
									
								
							@@ -180,6 +180,16 @@ Testing
 | 
			
		||||
 | 
			
		||||
Please refer to the [TESTING.md](TESTING.md) for instructions for testing the cookbook.
 | 
			
		||||
 | 
			
		||||
Berkshelf
 | 
			
		||||
=====
 | 
			
		||||
 | 
			
		||||
Berks will resolve version requirements and dependencies on first run and
 | 
			
		||||
store these in Berksfile.lock. If new cookbooks become available you can run
 | 
			
		||||
`berks update` to update the references in Berksfile.lock. Berksfile.lock will
 | 
			
		||||
be included in stable branches to provide a known good set of dependencies.
 | 
			
		||||
Berksfile.lock will not be included in development branches to encourage
 | 
			
		||||
development against the latest cookbooks.
 | 
			
		||||
 | 
			
		||||
License and Author
 | 
			
		||||
==================
 | 
			
		||||
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user