sensorario / ff

golang tool for #gitflow #semanticversioning #semver #git #cli #versioncontrol #developertool

• Autocompletion
• Commands
• Configuration
• Features

ff's Issues

add new rename command

removeRemotelyMerged

If true, delete also branches that are active pull request.

lowercase branch name

In some cases branch name is generated starting from sentences that contains upper and lower characters.

It could be better if branches will be always lower case.

add a littl web server

detect if current one is a node project

• check node_modules folder

git fetch origin --prune

Ignore some folder or files during creation of a git repository

Whenever new repository is create using ff, if not present a .gitignore file must be created!

• #52
• #49
• #50
• #51
• #54
• #55

undo

Is your feature request related to a problem? Please describe.
I'm always frustrated when It happens that I've to undo a commit.

Describe the solution you'd like
I want to avoid to write every time git revert HEAD whenever I mean "undo last commit"

Describe alternatives you've considered
The only alternative here is to type every time git revert HEAD. A fastest ff undo could be absolutely better

Add basic i18n support

• add 18n support
• add english language
• add italian language

default branch

• #57
• #58
• #59
• #60
• #61

detect if current one is a go project

delete remote merged branches

Delete all remote branches already merged. Deleted branches SHOULD be deleted also in all remote.

skip command whenever working directory is not clean

bad feedback after second attempt to tag same commit

Describe the bug
Trying to tag same commit twice no error nor feedback occurs.

To Reproduce
Simply ff tag twice same commit.

Expected behavior
The output should print a message like "commit already tagged"

Screenshots

prova

ask user if prefers main or master branch name

Oops! Bad configuration: development branch cannot be empty

Whenever ff run for the first time generate .git/ff.conf.json file in the following format:

{
  "features": {
    "tagAfterMerge": false,
    "disableUndoCommand": false,
    "stopAskingForTags": false,
    "applyFirstTag": false,
    "enableGitCommandLog": false,
    "forceOnPublish": false,
    "pushTagsOnPublish": false
  },
  "branches": {
    "historical": {
      "development": ""
    }
  }
}

This is absolutely bad!!! development branch should be, at least, current branch or master.

protect default branch forcing feature branches and so on

Poor feedback after repository initialization

It could be better if some feedback are given to the user. For example a message like "repository initialized" or something like that.

`ff push` should push alto tags

ff pull's output

There is no output when ff pull is executed. IS not clear what happened. Whether pull is done or not.

• log response in logs
• enable/disable output's log
• show pull command output

Change branch

Mov branch from feature/aaaaaa/master to feature/bbbbbb/master with ff rename or something like that

• #64
• #63

merge fix to all LTS

Whenever a bugfix is resolved in a LTS version, .. bring all updates in earlier LTS versions/branches so then all LTS will receive all fixes too.

So. When a tag is generated or when a job is complete and branch merged, whenever current branch is not development, ... current tag/commit MUST be merged on older version.

i.e.

If exists master and 1.3, ... each time a feature/xxxx/1.3 is merged into 1.3, ... 1.3 MUST be merge into master.

If exists master, 3.2, 2.1 and 1.0, a tag in 1.0 must be merged into 2.1, 3.2 and finally master.

All branches MUST be marked as LTS. Each branch must indicate next release:

{
    "lts" : [{
        "from" : "1.0",
        "to" : "2.1"
    },{
        "from" : "2.1",
        "to" : "3.0"
    }]
}

merge will stop in development branch.

Each "bump to version" may add an item in lts collection.

check of other files can be added to .gitignore file

split configuration in panels

add a panel to manage branche names

`ff complete` does not delete branch

Due to tag absence feature branch is not deleted when ff complete is called but any tag exists.

add web editor

Create a web editor for an easy way to update tha configuration

• #68
• #69
• #67
• #66

add missing symlink doc

if you symlink it as git-ff somewhere in you $PATH (Eg.: /usr/local/bin/git-ff), you could use it as a git custom command (Eg.: git ff authors)? :)

create .gitignore file if not exist

when repo is created, ask if default branch is master or main

missing alias for `git fetch -a`

old readme overwrite

On ff in non repository folder repository is created with empty README.md file and v0.0.0 tag. This behavior should be fixed because in case of non empty file, old readme file content is lost.

The expected behavior is that old readme file must be preserved. Actually is not!

toggle features

Make configuration options changeable from bash directly with ff toggle FeatureName command.

ff publish does not have outputs

add log folders or cache folders to .gitignore file

avoid tags whenever repository contains not commit

render html page with boolean flags for each configuration

push as alias for publish

Alias for publish.

list all committers

Is your feature request related to a problem? Please describe.
It could be interesting to see the list of commiter in a repository and listed by number of commit

Describe the solution you'd like
ff committers show list all the repo's committer and the number of commit done

Describe alternatives you've considered
Type every time git shortlog --summary --numbered

detect if current one is a php project

automatically close issues via commit message

Whenever a branch is completed and merged to master, apply the sentence 'close #num' so then the relative issues will be automatically closed on GitHub.

Running ff outside a git controlled folder gives unexpected results

If ff is run in a folder that is not a git controlled folder 'ff ' produces no results.

Would it not be better to display a message indicating that ff only works within a git controlled folder? Possibly displaying help about ff as well?

Avoid runtime error creating tag whenever same tag already exists

panic: runtime error: index out of range [2] with length 1

goroutine 1 [running]:
main.meta.patchVersion(0xc00011c080, 0x7, 0x0, 0x0, 0x1, 0x1)
	/Users/sensorario/Development/github.com/sensorario/ff/src/meta.go:41 +0xe4
main.meta.NextPatchTag(0xc00011c080, 0x7, 0x0, 0x0, 0x0, 0x0)
	/Users/sensorario/Development/github.com/sensorario/ff/src/meta.go:58 +0x67
main.tagStep.Execute(0xc000116000, 0x10)
	/Users/sensorario/Development/github.com/sensorario/ff/src/step_tag.go:39 +0x338
main.main()
	/Users/sensorario/Development/github.com/sensorario/ff/src/main.go:72 +0x38f

trying to commit on default branch, if protected, propose feature/ or other kind of branches

if not defined, ask what is the default branch

Add command to auto-tag HEAD as next minor release