Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the plugin aware of the current repo branch #28

Open
simonSlamka opened this issue Jul 13, 2022 · 3 comments
Open

Make the plugin aware of the current repo branch #28

simonSlamka opened this issue Jul 13, 2022 · 3 comments
Labels
💡 Enhancement New feature or request

Comments

@simonSlamka
Copy link
Contributor

If using git in the current project, the plugin should fetch the current branch name and pass it along to the waka heartbeats. If someone is using the Projects feature in WakaTime, this can give useful insights as to which branches is your time going against, but since the plugin doesn't report this information, WakaTime just says "Unknown".

image

@TheAshenWolf TheAshenWolf added the 💡 Enhancement New feature or request label Jul 18, 2022
@TheAshenWolf
Copy link
Owner

Sounds like a good idea!
Not sure when I get to it, but this would definitely be an improvement :)

@VerzatileDev
Copy link
Contributor

After testing it for a little while it does seem that in Unreal Engine 5

image

  • When the project is made with a template, that is what name is taken ( for what ever reason ) as the project name.
  • When its made from a blank document with the added name it reports it correctly as seen from reference.

image

image

With this in mind it does at least for me seem that the issue does not exist within Unreal Engine version 5 and the latest release available here: https://github.com/TheAshenWolf/WakaTimeForUE/releases/tag/1.2.5

Anyone here to Test Unreal 4 for context ?

  • Or the following issue should be closed.

@TheAshenWolf
Copy link
Owner

This issue is regarding the Branch - the current active git branch. Not the project name. So far I haven't found anything regarding branches in the CLI docs, but maybe it just automagically grabs the branch from the project, which would most likely mean that a project plugin would capture it, while editor plugin would not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants