22:21 <RubyDevguy> Can bundler write currently used gem versions to the Gemfile either as a comment or as a version restriction?

22:43 <slash_nick> RubyDevguy: is the Gemfile.lock not enough?

22:43 <slash_nick> it contains that info

22:51 <RubyDevguy> slash_nick: Its findable that way but seems easier/more readable to see it on each line in the normal gem file so you can update easier without all the research and back and forth, and to help lock in things upon a release or similar situation

22:52 <RubyDevguy> Just curious if there as a function similar to 'annotate' gem for documenting models, i could run say "bundle document' or something and each line ends up like: gem 'rails' #v4.2.4

22:56 <RubyDevguy> or even not a comment and actually just tagging the line with the current version being used

23:06 <jhass> RubyDevguy: did you look at the bundle outdated command?

23:07 <RubyDevguy> jhass: yes, thats where i got the idea, was just not sure if it coudl write the values in for you, before i took the time to go write them all in by hand

23:07 <Radar> Take the time to write them by hand if that's what you want.

23:07 <Radar> Gemfile.lock tells you that information.

23:07 <RubyDevguy> jhass: I thought it may be a feature just to save people time before deployment, if they are like me and dont write in version numbers when first putting in a gem

23:08 <jhass> that's what the lock is for

23:08 <jhass> commit it

23:09 <RubyDevguy> ya its commited, thanks