How to read tag that created in the new line? about git-changelog HOT 7 CLOSED

from git-changelog.

@rafinskipg would you point to the correct section to work on? I can see if I can work on it! thanks

from git-changelog.

also, I wonder if I can just keep everything after the feat(): as content, without parsing as another tag at least? is there an easy way to achieve that? or the place I can do some tweak to adjust that? thanks a lot @rafinskipg

from git-changelog.

hello @adamchenwei

I have done a test with your commit and i can get all as a body with the current version:

{ closes: [],
  breaks: [],
  hash: '',
  subject: 'make new ad',
  body: 'some note here\nreg(ad): need a walk through\n',
  type: 'feat',
  component: 'ad' }

What is the output you are getting?

About the other thing, getting 2 Section greps per commits, i'm not sure if its a good idea, it adds a lot of complexity. But the place to do it would be on the function organizeCommits in tasks/lib/organize-commits.js. I'm still not sure if its a feature that people will use, because the commit guideliness states to only do 1 thing per commit. Anyway, you can do a PR. If you need any help let me know (BTW : I'm refactoring stuff in the templating branch)

from git-changelog.

@rafinskipg ahhhhh cooool, so you are using \n , so what I did was doing git commit -m "feat(ad): make new ad -m "some note here" -m "reg(ad): need a walk through" I guess its different from just type in \n ... but when I do things like this, commit message shows me some thing super raw like feat(change log): new text\n AIR-1234\n reg(whole thing): goooooo through when I git log the commits.

Thought? Is that suppose to be? But I dont want \n to show up in the change log though, I want the actual new line. -m did help me achieve that, but seems git-changelog is seeing it as something else and eat it up for some reason. thought?

from git-changelog.

HI @adamchenwei i will test it later but the changelog is markdown so a \n would not be shown. I think you were doing it right at the first time. You don't have to type the '\n' stuff.

You can try to just do git commit and write the commit message with then line jumps there if you want.

But i'll tell you tomorrow, i should do some tests with more messages and generate the logs.

from git-changelog.

@rafinskipg yes, I actually tried use shift + enter that actually worked lololol, wonder why there is a difference

from git-changelog.