Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
Is there a way to get similar functionality to this one?
https://github.com/randy3k/Project-Manager
Even the out-of-the-box project manager workflow from Sublime would be a nice to have.
Right now I'm working with a structure of files that resembles something like:
-Workspace
- Folder1
- file1
- file2
- Folder2
- Folder3
- file1
- file2
- file3
- Folder4
We are managing the project in Jira (so, a ticket based kind of workflow if that makes sense).
I switch between tickets often times and I would like to save the "state/session/current workspace" (all the files that I was modifying at that time) for a specific task I was working on, so that I can also switch between the files that were involved for a particular task.
I guess I should note that the files I work on are spread across folders also.
I can easily save a Sublime's project and workspace for each ticket and switch to it, but I would like to do something similar in VSCode.
Edit
It's been quite some time since I asked, and I'm marking the new answer from #chachan
I also have been using it for a while now, works very well.
Found this one and works cool so far: https://github.com/alefragnani/vscode-project-manager
Currently there is no support for this in VS Code, but its a good idea for an extension.
Git Project Manager searches a directory (and subdirs) for git repos so you don't have to manage a list.
I am new to responding so forgive me if I am incredibly late. There is a project manager created by Alessandro Fragnani that can be obtained fromt he VCS Marketplace. I just installed and enabled it earlier today. Hope that helps.
I am using vscode-open-project
It is simple and fast.
More listed here:https://marketplace.visualstudio.com/search?
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
What I plan to do in some of my README.md files is provide hyperlinks to other sites that I cite. However, we all run into that problem when links die or get moved, and said link becomes invalidated. =(
Is there a github tool that can run nightly checks to see if all the links in a README.md file (or something similar) are working correctly?
What I'm looking for is something that has a feature similar to Travis CI, where a project could have a badge saying "link-passing" on the project's main github page. (Example: scikit-learn has those two classy looking "build-passing" badges.)
I think what you want to use is awesome_bot.
It doesn't provide the badge you want but it does check URLs in files.
From what I get from your question, Travis is actually enough to do the checking task.
I have already implemented it in this project. It's based on nodejs package named grunt-deadlink, Travis-CI configuration is also included. Unfortunately it doesn't support nightly test (as far as I know).
For shiny badge you can simply use this badge generator service.
Another tool that could also be integrated in your CI-Pipeline is mlc.
I integrated it in the pipeline of another project of mine
The mlc link checker is written in rust and fairly fast by using async calls to check web links.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I'm writing documentation for a GitHub project and wondering where should I write it to. There seems to be three options: GitHub Pages, GitHub Wiki or a set of Markdown files in the repository (e.g. under docs/ directory) similar to the README.md. Understandably I don't want to write the same documentation to multiple places so I have to pick one.
So what are the differences, pros and cons between the options? Any experience or thoughts about using them especially for project documentation? Also is there other options in addition to the three?
that is a very good question which I personally decide on a change-frequency and number-of-contributors basis.
As an example: in one of our projects (a c++ library) we create a HTML documentation with doxygen once in a while (e.g. while updating the master release branch). That's a perfect match for quasi-static gh-pages. In addition you get a sub domain for it http://<user>.github.io/<project>/ and you can register your own domains on top of it.
An other project contains developer and user documentation (a C++ program). I personally prefer to provide a main workflow for developers in .md files to keep them consistent with the mainline development. Changes will be reviewed by pull requests first.
But for user documentation we choose the build-in wiki since it is very easy to edit and modify - one can even allow modifications by non-members of a team.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
lazy dont have to read this
I have to work on an old netbeans project which is kinda messy. The previous autor changed a lot in some .properties and .xml files and add ant scripts. (Aplication is designed for Websphere, and it have some requirements)
Unfortunatly today doesn't work. Some important values was stored in private.properties (I dont know what exacly was), ant script don't run, and few versions issue apper. So first I have to tidy this mess, but I dont know about netbeans project well. Unfortunatly I have problem to find documentation to all of it.
Netbeans project is based on ant project. Fortunatley ant have manual here: http://ant.apache.org/manual/index.html . But (I assume that) 'nbproject' folder and its inner files are not part of ant project. I can't find documentation about it. Maybe I blind or something, but I didn't found it on NetBeans side. IMHO netbeans side is kinda messy as well.
straight to the point
I am searching for documentation for netbeans project, where will be written about files project.xml, project.properties etc. What they contain and even how to write them on your own.
This document explains freeform project configuration in detail. You should be able to find what you need in there. If I were in your position, I would create a new project that has all the frameworks like your original project and then look at the project metadata files of the new project for some direction. IMO this is far easier than trying to author the project.xml files from scratch.
http://netbeans.org/kb/articles/freeform-config.html
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I have searched around and can't find anything, so could anyone help me with getting notepad++ to work seamlessly with Github. I would like to be able to open notepad++ and be able to work on files, then when I save (or live) it will show on Github. I have installed everything they say I need to and have the README, but that's all.
Have you tried this plugin for Notepad++?
http://forum.lowyat.net/topic/1358320/all
You can not save directly on github but you can save and then commit these modified files.
This is really an old question, but I just bumped into it today and thought I'd share my strategy, as the plugin proposed here requires also TortoiseSVN, which is a setup that I don't find as fluid and easy to use as my alternative.
After finding that there's no "stand-alone" plugin you can get for this, I started using GitHub Desktop App. This enables you to set repositories locally, make commits, pulls, pushes, etc. Just login with your account, and then create a local repository for your project.
After creating the repository, just open the files you wish to edit with Notepad++. Make some changes, save and use the GitHub Desktop Application to do all GitHub related stuff. Opposed to the plugin, this app provides a full featured interaction with GitHub.
By the way, if you have two monitors, or a big one, you can just have the two applications open side by side, which emulates similar setups you can find in advanced IDEs (Eclipse, for example). I find this to be even more convenient and fluid than having to open a separate plugin dialogue for doing my Git related stuff. The GitHub Desktop application will even refresh automatically, without any interaction being required from you, after you make any editions to the files (using Notepadd++) or any changes in the file structure (add, rename, move, delete files).
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I need a simple, web-based version control tool. 'Version Control' probably implies a lot of functionality I don't need such as diff and merge.
Basically, I have a lot of non-programmer types working on binary files (think Photoshop PSDs), and I would just like a way to check them out and in, and keep previous versions.
Web-based would be ideal, I just want something better than nested folders on a shared drive.
Suggestions?
You could try asvcs: it's web-based and very simple. My advice would be to try one of the known solutions (svn, git, mercurial, even bazaar) and use only the features you need.
Dropbox provides a web interface and can be used as a simple version control system.
Try building something around git. (Or maybe set up a private github account.)
Springloops has what you're looking for. However, it's a paid service. Integrates nicely with Basecamp
You could also use Dropbox. There's version control of sorts. But history is kept only for 1 month.
And there's github
I know through experience that Atlassian's Confluence wiki solution will do versioning for binary uploads. I'm sure there are probably other open source alternatives available as well.