fetch the underlying repository (either from filesystem or it can be made available through Git exporter). Prior to this, you might want to commit any pending changes (see 惰性提 交). This can be achieved setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the API key. # Commit all pending changes in Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside Weblate to automate this. What are the options for pushing changes back upstream? This

fetch the underlying repository (either from filesystem or it can be made available through Git exporter). Prior to this, you might want to commit any pending changes (see 惰性提 交). This can be achieved setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the API key. # Commit all pending changes in Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside Weblate to automate this. What are the options for pushing changes back upstream? This

fetch the underlying repository (either from filesystem or it can be made available through Git exporter). Prior to this, you might want to commit any pending changes (see Lazy commits). This can be achieved setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the API key. # Commit all pending changes in Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside Weblate to automate this. What are the options for pushing changes back upstream? This

fetch the underlying repository (either from filesystem or it can be made available through Git exporter). Prior to this, you might want to commit any pending changes (see Lazy commits). This can be achieved setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the API key. # Commit all pending changes in Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside Weblate to automate this. What are the options for pushing changes back upstream? This

fetch the underlying repository (either from filesystem or it can be made available through Git exporter). Prior to this, you might want to commit any pending changes (see 惰性提交). This can be achieved in setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the API key. # Commit all pending changes in Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside Weblate to automate this. What are the options for pushing changes back upstream? This

fetch the underlying repository (either from filesystem or it can be made available through Git exporter). Prior to this, you might want to commit any pending changes (see 惰性提交). This can be achieved in setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the API key. # Commit all pending changes in Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside Weblate to automate this. What are the options for pushing changes back upstream? This

fetch the underlying repository (either from filesystem or it can be made available through Git exporter). Prior to this, you might want to commit any pending changes (see 惰性提 交). This can be achieved setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the API key. # Commit all pending changes in Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside Weblate to automate this. What are the options for pushing changes back upstream? This

fetch the underlying repository (either from filesystem or it can be made available through Git exporter). Prior to this, you might want to commit any pending changes (see 惰性提 交). This can be achieved setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the API key. # Commit all pending changes in Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside Weblate to automate this. What are the options for pushing changes back upstream? This

fetch the underlying repository (either from filesystem or it can be made available through Git exporter). Prior to this, you might want to commit any pending changes (see 惰性提交). This can be achieved in setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the API key. # Commit all pending changes in Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside Weblate to automate this. What are the options for pushing changes back upstream? This

fetch the underlying repository (either from filesystem or it can be made available through Git exporter). Prior to this, you might want to commit any pending changes (see 惰性提 交). This can be achieved setup, access to the Weblate repository might require authentication. When using the built in Git exporter in Weblate, you authenticate with your username and the API key. # Commit all pending changes in Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside Weblate to automate this. What are the options for pushing changes back upstream? This