enter image description here
I tried this, but there's an error
enter image description here
Error message says
No .platform/services.yaml file found in the repository.
No .platform/routes.yaml file found in the repository.
enter image description here
but It's definitely there.
i don't understand...
Without seeing your repository, my guess is that those two files haven't been committed to the repository (the ! next to each of them in your third image). You can double-check by doing git status. If they are definitely committed, hop into our slack workspace and/or submit a support ticket so we can take a look at what's happening.
It sounds like you use visual studio and you need to:
add the files to git
commit the files to git
push the file to platform.sh
If you have trouble with this, you may want to use one of the existing template https://docs.platform.sh/development/templates.html and the modify these files.
In general, it is easier to start from a functional solution than a non working one ;-)
Related
We recently migrated from using Subversion and Trac to Git and GitLab. We successfully migrated all of our old data.
I'm still trying to learn GitLab and generally like it better than Trac, but one thing I don't like as much is that when you reference a GitLab Issue in the git commit, it adds a reference and link to that commit under the issue, but you have to browse to the commit itself to see the associated Git commit message.
In Trac, we had it configured such that the Subversion commit messages were all displayed in the Trac ticket with the commit link, so it was easier to view all the relevant information for that ticket in one place.
Is there a way to configure GitLab to display the Git commit message with the Git commit link that shows up under Issues? The message does show up in the commit list, but not on a referenced Issue.
I thought about trying to use a server hook to generate a note with the Git commit message when a commit is made, but just wondering if there is an easier/better way to accomplish this?
There is no built-in way to show the commit message of a crosslinked commit in the issue log. After all, commits are handled the same way as any other mentions: in the issue's history/mention log.
While the example in GitLab's documentation unfortunately misses the opportunity to show an example of a mention in the commit, here's an issue from GitLab itself with a mention. This commit also shows how mentions often get used within commits—with keywords:
Merge branch '65375-broken-master-gitlab-svg-path-test-failing' into 'master'
Update failing jest snapshot
Closes #13186
See merge request gitlab-org/gitlab-ee!14933
These kind of commits close the specific issue and don't require any further user action. Adding that kind of noise to the discussion/comment section of an issue is, in my opinion, only cluttering the discussion between actual humans*. However, the commit still shows up in the log and is clickable and hoverable.
To get back to your question:
Is there a way to configure GitLab to display the Git commit message with the Git commit link that shows up under Issues?
If you hover over the linked commit, then you'll get the commit's subject. There's nothing more that can be achieved within GitLab itself.
I thought about trying to use a server hook to generate a note with the Git commit message when a commit is made, but just wondering if there is an easier/better way to accomplish this?
If you follow the usual commit/merge message based issue closing and use [Closes?|Fix(es)?] #issue in your commit message, you may end up with more noise in the comments than you would like too.
* well, except for some bots
I am not sure this is the right forum for this question.
I use Gitlab for storing all my codes, version control, etc. since I don' trust my PC. It suddenly dawned on me, will my account get deleted if I don't access it for a while or is there a limit to size of project that I can push there, etc. Basically use Gitlab for file storage also.
I didn't find any relevant answers on google. Can you please point me to these answers?
Gitlab has a maximum auf 10G/repo. If you have larger files you should use Git LFS otherwise git is for small code files. So i don't think that your account is deleted if you are inactive. Otherwise you should get an e-mail with a notification.
https://about.gitlab.com/blog/2015/04/08/gitlab-dot-com-storage-limit-raised-to-10gb-per-repo/
https://docs.gitlab.com/ee/administration/lfs/manage_large_binaries_with_git_lfs.html
I have a sever on heroku. I'm making changes on my project (for ex. adding something inside my JSON file). I'm pushing my changes on heroku/master branch like this:
git add .
git commit -am "changes in json file"
git push heroku master
I'm getting "Everything up-to-date". When I'm reloading the server the changes that I made don't appear, it makes sense because if I'm trying to push to my heroku master brench I'm gerring "Everything up-to-date" but I'm expecting to show me the changes and to restart the server automatically.
Can you help me?
For any additional informations please ask me!
It works!
I don't know what I did to solve the problem, it solved after I made a new project following this tutorial: https://www.youtube.com/watch?v=P86N9FqNqso&list=LL69VX7JLGdfJjh-p8M1RzVw&index=2&t=0s
It might be possible due to the fact that I wasn't in the right folder, I didn't check the folder I was in, I'm not saying that that was my problem but I consider it a possibility.
It works now, thanks for helping and if you have the same problem I can suggest to you rechecking if you are in the right folder, your project folder, or check the tutorial I linked above.
In subversion I'm trying to commit a project but running into an issue.
The error I get is
Illegal repository URL ''
How come I can run update, but commit on the same tree shows that?
Try this, it worked for me:
Create a folder.
Right button over folder and create repo here.
When pop up appears select create folder structure and then open folder.
When repository browser appears you see tags branch etc, right button again and create folder but now with tool tortoise.
Update you file to folder.
After some hunting around it seems that a few other people have experienced some sort of local corruption at the top level their checked out project directory which is where I was committing from.
I followed the same procedure that was used to solve those cases which is to back up the sources. Check out the project again. Finally copy the changed files back over the freshly checked out copy. Check it builds correctly. And then commit that.
It seemed to solve it for me.
I cannot figure out why I get this error during check-in. I checked in successful only a few hours ago so not sure why now it's complaining
Error: Commit failed (details follow):
Error: Checksum mismatch for
Error: 'C:\sss\sss\trunk\xxxx\.svn\text-base\Header.ascx.svn-base'; expected:
Error: '3cee96f580409a1711a47541a07860dd', actual: 'a5fc0f8819b88bf32ab38d4c9a6b0654'
Error: Try a 'Cleanup'. If that doesn't work you need to do a fresh checkout.
I got latest and also performed a clean-up which said successful so not sure what else to do.
Something has gotten out of sync or has become corrupt, and because it's in your .svn BASE directory, unless you are confident tinkering with this, you're probably better off deleting the parent of the .svn directory and then perform an update. Of course, take a backup or see if an export works before doing this, so you don't lose any changes.
FWIW, I get this sometimes with our library references where Visual Studio seems to keep a lock on some files (even though it's not compiling) and won't let me update them. I believe this is related to the xml documentation files.
Note: Subversion 1.7+ implements a new working copy approach which centralises the meta data, and it now has a single .svn directory at the root of your working copy. Your best bet is a cleanup, failing that a fresh checkout into another directory and export or file copy the corrupted working copy except for the .svn directory, over to the fresh checkout, and commit any local changes.
Looks like one of your SVN files is corrupt. First, check-in everything that can safely be checked in, and make sure to backup everything. Then fix the offending file - usually this involves deleting it from your repository. This should be okay if you're checking in a new version anyway.
I received a similar error after our project repository was moved to a new server. Try reverting your file and reapplying your changes.
I had same problem after googling for some help found articles that suggested to override the checksum in the .svn\entries file. But in that file the checksum was actually as the the expected one in the error message.
To fix the problem, I navigated to .svn\text-base dir of problem file's directory and found out that there's a copy of the file i was trying to check in changes for. I opened that file in Notepad++ and replaced it's content with content of the file to be commited and i was able to commit afterwards.
But just in case, make a backup copy of the .svn\text-base file.
I think this happened because i did an svn update before commit because it complained that my version is outdated. Anyway, it's fixed for me and hope my solution helps someone else too.
With Tortoise SVN, I choose to delete the file in Repo Browser.
First back up the problem file. and use Repo Browser delete the problem file in it, then update local folder so the file in local folder is deleted. Then copy back the backup file and Add > Commit, then I can update successfully.
The disadvantage of this method is the history of this file will be removed.
Also see another post.